Serveur MCP
mitosis
ai.mitosislabs/mitosis
Ce que fait ce MCP
Provides agent-memory platform capabilities including documentation search, platform status, pricing information, and agent skills.
Capacités
Outils
20
outils
cortex_accept_goal
Save a settled goal
Saves a settled goal into the memory's goal library, along with the recipe it was designed with, and returns its goal id. Still extracts nothing: cortex_choose_enrichment with choice=describe_goal and that id in goal_ids is what runs it on a source.
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['draft_id'], 'properties': {'draft_id': {'type': 'string', 'description': 'From cortex_create_goal or cortex_answer_goal.'}}, 'additionalProperties': False}
cortex_answer_goal
Record the user's answer about a goal
Records the user's answer to the questions from cortex_create_goal, keyed by question id. `{"*":"skip"}` is the answer for a user who says to go ahead with whatever Mitosis thinks best. This is the last round: the reply carries answer_required=false and no further questions, because Mitosis asks about a goal once.
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['draft_id', 'answers'], 'properties': {'answers': {'type': 'object', 'description': 'Question id to the chosen option, or the user\'s own words. {"*":"skip"} takes the first option of each.', 'additionalProperties': {'type': 'string'}}, 'draft_id': {'type': 'string', 'description': 'From cortex_create_goal.'}}, 'additionalProperties': False}
cortex_ask
Search the user’s memory
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 (universal ids), freshness, and `cited_graph_url`, a deep link showing the cited nodes highlighted in the user's own graph. A later cortex_remember links to what was retrieved here. Retrieval returns nearest matches rather than a thresholded set, so a question whose answer lives in an unconnected source comes back with the closest thing in the memory instead of with nothing. A `source_gap` object in the result names that case: the memory holds data, but the source that would answer this question is not connected. It lists those sources, what each answers, and one connect link, on `cta`. A `possible_source_gap` object is the conditional form — results exist but may be near-misses rather than an answer. A result carrying neither means the answer is genuinely absent from the memory rather than merely unretrieved.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['question'], 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 10).'}, 'since': {'type': 'string', 'description': 'RFC3339 lower bound on item time.'}, 'until': {'type': 'string', 'description': 'RFC3339 upper bound on item time.'}, 'question': {'type': 'string', 'description': 'Natural-language question or search query.'}, 'source_table': {'type': 'string', 'description': 'Restrict to one source table, e.g. gmail_messages.'}}, 'additionalProperties': False}
cortex_choose_enrichment
Record what the user wants pulled out of a source
Record what the user wants Mitosis to pull out of a data source. A newly saved source WAITS: it is stored and searchable, but nothing is extracted from it until the user answers. When any save/ingest result carries `choice.choice_required: true`, ask the user its `question` and present EXACTLY two options: "Standard" (Mitosis extracts the people, companies, projects, topics, dates, and how they connect) or "Describe your goal" (the user says what they want extracted). Then call this tool with their answer. Never choose for the user and never infer an answer from silence. After cortex_list_goals, pass `goal_ids` to run those saved recipes on this source now. A brand-new goal is enough: Cortex writes the extract contract and starts extracting. Call it without `choice` to read the current state.
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['feed_key'], 'properties': {'goal': {'type': 'string', 'description': "A new goal, in the user's words. Required with describe_goal unless goal_ids is set."}, 'choice': {'enum': ['standard', 'describe_goal'], 'type': 'string', 'description': '"standard", or "describe_goal" together with `goal` and/or `goal_ids`. Omit to read the current state.'}, 'feed_key': {'type': 'string', 'description': 'The source, from `choice.feed_key` in the save/ingest result.'}, 'goal_ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Saved goals from cortex_list_goals to run on this source.'}, 'idempotency_key': {'type': 'string', 'description': 'Optional retry key; the same key never records twice.'}}, 'additionalProperties': False}
cortex_connectable_sources
Sources this memory could connect
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 user works in.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}, 'additionalProperties': False}
cortex_connect_link
Connect link for one source
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 is the caller's judgment, made from each entry's `answers` and `tags`. `link_text` names, in the user's own words, what connecting answers — it becomes the connect page's title. Connecting itself is an authorization the user performs on that page; this tool only returns the link.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['source_id'], 'properties': {'link_text': {'type': 'string', 'description': "Link text naming what connecting answers, in the user's words. Becomes the connect page title. Omit for a generic label."}, 'source_id': {'type': 'string', 'description': 'Source id exactly as listed, e.g. google-workspace, github, notion.'}}, 'additionalProperties': False}
cortex_create_goal
Design a new goal with the user
Designs a goal from the user's own words: what Mitosis should pull out of their data, and how the things in it connect. Returns a read-back of what Mitosis understood, with a real example from their data, and sometimes one round of questions it could not decide from the words alone. `answer_required: true` means the goal is waiting on the user: the `questions` carry the options Mitosis can act on, and cortex_answer_goal records the answer. `answer_required: false` means the design is settled and cortex_accept_goal saves it. Nothing is extracted from any data here. Designing a goal, saving it, and running it on a source are three separate operations.
Schéma d’entrée
{'type': 'object', 'required': ['goal'], 'properties': {'goal': {'type': 'string', 'description': 'What the user wants out of their data, in their own words.'}, 'feed_keys': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Optional sources to draw the read-back example from. A goal belongs to the memory, not to one source.'}}, 'additionalProperties': False}
cortex_ingest
Add a document to the user’s memory
Push a document into this memory so its text becomes searchable. Pass the file text as content with a filename, or several items in files (each with name and content). Default feed is local_files. The result may carry choice.choice_required: when that is true the source is stored and searchable but waiting for the user to pick Standard or Describe your goal; record that answer with cortex_choose_enrichment. This server cannot read a local filesystem — paths belong on the stdio MCP (mi-cortex-mcp).
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {'feed': {'type': 'string', 'description': 'Feed identity (schema ext_<feed>). Letters, digits, underscore. Default local_files.'}, 'files': {'type': 'array', 'items': {'type': 'object', 'properties': {'name': {'type': 'string'}, 'content': {'type': 'string'}}}, 'description': 'Several documents: [{name, content}, ...].'}, 'title': {'type': 'string', 'description': 'Override title when ingesting a single file.'}, 'content': {'type': 'string', 'description': 'Document text. Required with filename.'}, 'filename': {'type': 'string', 'description': 'Name for inline content (required with content).'}}, 'additionalProperties': False}
cortex_ingest_conversation
Save a conversation into the user’s memory
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 reliably (cannot-answer / connect-a-source replies — they describe missing data, not knowledge), tool call outputs, hidden reasoning, connect links, and anything resembling credentials or secrets. Re-ingesting the same session_id updates it instead of duplicating. Split very long conversations across calls.
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['turns'], 'properties': {'title': {'type': 'string', 'description': 'Short human title for the conversation.'}, 'turns': {'type': 'array', 'items': {'type': 'object', 'required': ['role', 'text'], 'properties': {'role': {'enum': ['user', 'assistant'], 'type': 'string'}, 'text': {'type': 'string'}}, 'additionalProperties': False}, 'description': 'The conversation, in order. User and assistant text only — verbatim.'}, 'session_id': {'type': 'string', 'description': '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.'}}, 'additionalProperties': False}
cortex_list_goals
List saved goals for this memory
The saved goals this office already asked Mitosis to pull out of data. Call this before choosing enrichment on a new source so you can offer those goals (the user can pick several) instead of inventing a new one. Last-used goals are first. Then pass the chosen ids as goal_ids to cortex_choose_enrichment.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}, 'additionalProperties': False}
cortex_manifest
What the user’s memory contains
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 with cortex_ask.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}, 'additionalProperties': False}
cortex_recall
Semantic search of the user’s memory
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.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['query'], 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 10).'}, 'query': {'type': 'string', 'description': 'Search text.'}}, 'additionalProperties': False}
cortex_remember
Save a fact to the user’s memory
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. If the result carries `choice.choice_required: true`, the memories source is waiting for the user’s enrichment choice: ask `choice.question`, offer exactly "Standard" or "Describe your goal", and record the answer with cortex_choose_enrichment.
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['text'], 'properties': {'kind': {'type': 'string', 'description': "e.g. 'decision', 'observation', 'task-outcome'."}, 'text': {'type': 'string', 'description': 'The fact or conclusion itself — one self-contained statement.'}, 'confidence': {'type': 'number', 'description': '0..1, weights the provenance edges.'}, 'source_universal_ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Universal ids from a previous cortex_ask that this fact came from.'}}, 'additionalProperties': False}
cortex_status
Memory freshness and coverage
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".
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}, 'additionalProperties': False}
fetch
Read one item from the user’s memory
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.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The id of an item, exactly as returned by `search`.'}}, 'additionalProperties': False}
Schéma de sortie
{'type': 'object', 'required': ['id', 'title', 'text', 'url', 'metadata'], 'properties': {'id': {'type': 'string', 'description': 'The id that was requested.'}, 'url': {'type': 'string', 'description': 'Absolute link to this record on the user’s memory graph.'}, 'text': {'type': 'string', 'description': 'The record’s full contents as plain text. May be empty if the record has none.'}, 'title': {'type': 'string', 'description': 'Human-readable name of the record.'}, 'metadata': {'type': 'object', 'properties': {'source': {'type': 'string', 'description': 'Source table the record came from.'}, 'fetched_at': {'type': 'string', 'description': 'When Mitosis last ingested it.'}, 'integration': {'type': 'string', 'description': 'Integration that supplied it, e.g. google-workspace.'}, 'sensitivity': {'type': 'string', 'description': 'Sensitivity label, where the source sets one.'}}, 'description': 'Provenance, where known. Any key may be absent.', 'additionalProperties': False}}, 'additionalProperties': False}
get_platform_status
Get platform status
Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {'service': {'enum': ['website', 'api', 'mcp'], 'type': 'string', 'description': 'Return only this service. Omit for all services.'}}, 'additionalProperties': False}
get_pricing
Get Mitosis pricing
Get current Mitosis plans, prices, credit allowances, metered rates, and add-ons. Use when comparing costs or recommending a plan.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {'plan': {'enum': ['solo', 'team', 'scale', 'business'], 'type': 'string', 'description': 'Return only this plan. Omit for all plans.'}}, 'additionalProperties': False}
list_skills
List agent skills
List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {'tag': {'type': 'string', 'description': 'Filter skills by tag (e.g. "backup", "restore", "schedule"). Omit for all.'}}, 'additionalProperties': False}
search
Search the user’s memory (deep research)
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 read the full record.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': 'What to look for, in natural language.'}}, 'additionalProperties': False}
Schéma de sortie
{'type': 'object', 'required': ['results'], 'properties': {'results': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'title', 'url'], 'properties': {'id': {'type': 'string', 'description': 'Opaque record id. Pass it to `fetch` to read the full record.'}, 'url': {'type': 'string', 'description': 'Absolute, user-openable link: the original item where the source exposes one, otherwise a link to the record on the user’s memory graph.'}, 'title': {'type': 'string', 'description': 'Human-readable name of the record.'}}, 'additionalProperties': False}, 'description': 'Ranked matches from the user’s memory, best first.'}}, 'additionalProperties': False}
search_docs
Search Mitosis docs
Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['query'], 'properties': {'limit': {'type': 'integer', 'default': 5, 'description': 'Max results (default 5, max 20)'}, 'query': {'type': 'string', 'description': 'Search terms, e.g. "connect google workspace"'}}, 'additionalProperties': False}
Historique
Modifications récentes des outils
Ajouté
cortex_accept_goal
23 September 2026 02:51
Ajouté
cortex_answer_goal
23 September 2026 02:51
Ajouté
cortex_create_goal
23 September 2026 02:51
Ajouté
cortex_list_goals
21 September 2026 02:58
Modifié
cortex_choose_enrichment
21 September 2026 02:58
Ajouté
cortex_ingest
21 September 2026 02:58
Ajouté
list_skills
17 September 2026 07:57
Ajouté
search_docs
17 September 2026 07:57
Ajouté
get_platform_status
17 September 2026 07:57
Ajouté
get_pricing
17 September 2026 07:57
Ajouté
fetch
17 September 2026 07:57
Ajouté
search
17 September 2026 07:57
Ajouté
cortex_choose_enrichment
17 September 2026 07:57
Ajouté
cortex_ingest_conversation
17 September 2026 07:57
Ajouté
cortex_remember
17 September 2026 07:57
Ajouté
cortex_connect_link
17 September 2026 07:57
Ajouté
cortex_connectable_sources
17 September 2026 07:57
Ajouté
cortex_status
17 September 2026 07:57
Ajouté
cortex_manifest
17 September 2026 07:57
Ajouté
cortex_recall
17 September 2026 07:57
Ajouté
cortex_ask
17 September 2026 07:57
Découvrir
Serveurs MCP similaires
VaultCrux Memory Core
io.github.CueCrux/vaultcrux-memory-core
Stores and evaluates agent memory, facts, decisions, constraints, expertise, checkpoints, contradictions, and delegation readines…
AgentBoard
app.agentsknow/agentboard
Provides agents with private memory, knowledge pages, evidence, posts, tasks, coordination spaces, proposals, voting, and resumab…
agent4.io
io.agent4/agent4-tenant
Manages grounded business agents, knowledge bases, skills, connected MCP tools, public shares, and structured interactive storyli…
Swarmspace
net.swarmspace.www/swarmspace
Supports persistent agent identities, shared knowledge search, public discussions, troubleshooting references, file storage, pres…
Remnant — Collective Memory & Evidence-Backed Trust for AI Agents
com.dedale-bi.remnant/remnant
Provides searchable collective memories, public agent discovery, provenance inspection, and cryptographically verifiable trust pa…
chp
io.github.capabilityhostprotocol/chp
Provides documentation, examples, capability descriptors, adapters, and adoption guidance for the Capability Host Protocol and it…
agtrepo-memory
io.github.agtrepo/agtrepo-memory
Stores, retrieves, extends, and shares encrypted persistent text memories for AI agents using paid access controls.
guide-registry
guide.fleetleader/guide-registry
Provides read-only access to a Bicycle Guide registry, including guides, taxonomy, publication status, and capability relationshi…