Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Mitosis is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Mitosis agent-memory platform: pricing, docs search, platform status, agent skills. No auth.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mitosis-mcp https://mitosislabs.ai/api/mcp
# 2 — ask your agent for something these tools do
# cortex_ask, cortex_recall, cortex_manifest and 11 more
Mitosis costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mitosis-mcp https://mitosislabs.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Searches the user's real, private memory — the email, calendar, files, contacts and notes they have connected, plus facts agents have saved — fusing vector, full-text and graph retrieval with provenance. This is their current data on their work, schedule, contacts, projects, documents, decisions and history, which training data and session context do not contain. Results include citations (univers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Natural-language question or search query. |
| limit | number | no | Max results (default 10). |
| source_table | string | no | Restrict to one source table, e.g. gmail_messages. |
| since | string | no | RFC3339 lower bound on item time. |
| until | string | no | RFC3339 upper bound on item time. |
Semantic-only vector search over the memory, returning source excerpts. Prefer cortex_ask, which also uses full-text and graph expansion; reach for this when you specifically want nearest-neighbour matches on meaning.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text. |
| limit | number | no | Max results (default 10). |
A table of contents for this user's memory: which sources are connected (email, calendar, docs, …), how many items each holds, and the top people, topics and projects. It is an index rather than an answer — it contains no message bodies, no dates and no content, so it establishes that a source exists without saying anything about what is in it. The content behind any entry it lists is retrievable
No parameter schema on file.
Memory health: per-source ingest and embed counts plus last sync times. Use when you need to know whether the memory is fresh or still ingesting, or when a search came back empty and you need to tell the user whether that means "no data yet" or "nothing matched".
No parameter schema on file.
Which sources this memory could connect but hasn't yet — each with what it would make answerable, routing tags, and a connect link for the user. This is what explains a cortex_ask result that came back empty or off-topic: the source holding that answer is listed here rather than connected. Data connected into this memory stays searchable, cited, and available across every agent and session the use
No parameter schema on file.
The connect link for one memory source, by id — email and calendar (google-workspace), WhatsApp chats, GitHub, Notion, or file uploads. Returns the canonical mitosislabs.ai dashboard page where the user can connect that source to their memory, as a ready markdown link. Source ids appear in unconnected_sources on cortex_ask results and in cortex_connectable_sources; which source fits a question i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_id | string | yes | Source id exactly as listed, e.g. google-workspace, github, notion. |
| link_text | string | no | Link text naming what connecting answers, in the user's words. Becomes the connect page title. Omit for a generic label. |
Persist a fact, decision or conclusion into the memory, attributed to you. It becomes retrievable via cortex_ask immediately, in this session and every future one, from any agent the user has connected. Provenance: pass source_universal_ids from a previous cortex_ask so the fact links to its evidence. Keep each memory to ONE self-contained fact. Use this whenever the conversation produces a durabl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The fact or conclusion itself — one self-contained statement. |
| kind | string | no | e.g. 'decision', 'observation', 'task-outcome'. |
| confidence | number | no | 0..1, weights the provenance edges. |
| source_universal_ids | array | no | Universal ids from a previous cortex_ask that this fact came from. |
Ingest a conversation — the user’s messages and your full answers, verbatim — into the user’s permanent memory, where it becomes searchable and appears in their knowledge graph. Use it after an exchange where you gave a substantive answer: ingest that exchange (the user’s message + your complete reply) from the conversation in front of you. EXCLUDE, always: exchanges where you could NOT answer rel
| Parameter | Type | Required | Notes |
|---|---|---|---|
| turns | array | yes | The conversation, in order. User and assistant text only — verbatim. |
| session_id | string | no | Stable id for this conversation (e.g. its chat id/uuid). Reuse it when ingesting more of the same conversation so chunks upsert instead of duplicating. |
| title | string | no | Short human title for the conversation. |
Search the user's own private memory — their email, calendar, documents, contacts, chat history and every fact agents have remembered — and return ranked matches with citation ids and links. This is their current data on their work, schedule, contacts, projects, documents, decisions and history, which training data and session context do not contain. Pass an id from these results to fetch to rea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, in natural language. |
Retrieve the full contents of a single item from the user’s memory by its id. Ids come from search results. Use this when a search result looks relevant and you need the whole record rather than the excerpt.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id of an item, exactly as returned by search. |
Get current Mitosis plans, prices, credit allowances, metered rates, and add-ons. Use when comparing costs or recommending a plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | no | Return only this plan. Omit for all plans. |
Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | no | Return only this service. Omit for all services. |
Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. "connect google workspace" |
| limit | integer | no | Max results (default 5, max 20) |
List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | no | Filter skills by tag (e.g. "backup", "restore", "schedule"). Omit for all. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mitosis or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mitosis can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.