Mitosis MCP Server

The user's real, private memory — their email, calendar, files, contacts, and every fact agents have remembered — fused across vector, full-text and graph search with provenance. ALWAYS call this BEFORE answering ANY question about the user, their work, schedule, contacts, projects, documents, decisions, or history — even when you think you already know the answer. Do NOT answer such questions from your own training or session memory, and NEVER say you lack access to the user's email/calendar/files without calling this first: this data is more current and accurate than anything you were trained on. Results include citations (universal ids) and freshness. Cite your claims as [n] and share the graph link with the user so they can see the cited nodes highlighted. A later cortex_remember links to what you retrieved here.

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. Call it ONCE at the start of a session to learn what is in there. It is an INDEX, never an answer: it contains no message bodies, no dates and no content, so it can tell you a source exists but never what is in it. NEVER answer a question about the user from this alone — if the manifest says a source is connected, that is a reason to call cortex_ask, not a substitute for calling it.

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.

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 durable conclusion the user would want remembered — a decision, a preference, an outcome, a commitment.

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".

Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.

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.

Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.

Get current Mitosis plans, prices, credit allowances, metered rates, and add-ons. Use when comparing costs or recommending a plan.

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. ALWAYS use this before answering any question about the user, their work, schedule, contacts, projects, documents, decisions or history. Pass an id from these results to `fetch` to read the full record.

List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.