cortex_ask
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 m
Показать схему аргументов
{
"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_recall
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.
Показать схему аргументов
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "number",
"description": "Max results (default 10)."
},
"query": {
"type": "string",
"description": "Search text."
}
},
"additionalProperties": false
}
cortex_manifest
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.
Показать схему аргументов
{
"type": "object",
"properties": [],
"additionalProperties": false
}
cortex_status
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".
Показать схему аргументов
{
"type": "object",
"properties": [],
"additionalProperties": false
}
cortex_connectable_sources
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.
Показать схему аргументов
{
"type": "object",
"properties": [],
"additionalProperties": false
}
cortex_connect_link
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 author
Показать схему аргументов
{
"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_remember
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 enr
Показать схему аргументов
{
"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_ingest
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).
Показать схему аргументов
{
"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
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-ing
Показать схему аргументов
{
"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_create_goal
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 ru
Показать схему аргументов
{
"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_answer_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.
Показать схему аргументов
{
"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_accept_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.
Показать схему аргументов
{
"type": "object",
"required": [
"draft_id"
],
"properties": {
"draft_id": {
"type": "string",
"description": "From cortex_create_goal or cortex_answer_goal."
}
},
"additionalProperties": false
}
cortex_choose_enrichment
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,
Показать схему аргументов
{
"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_list_goals
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.
Показать схему аргументов
{
"type": "object",
"properties": [],
"additionalProperties": false
}
search
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.
Показать схему аргументов
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "What to look for, in natural language."
}
},
"additionalProperties": false
}
fetch
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.
Показать схему аргументов
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The id of an item, exactly as returned by `search`."
}
},
"additionalProperties": false
}
get_pricing
Get current Mitosis plans, prices, credit allowances, how usage is charged, and add-ons. Use when comparing costs or recommending a plan.
Показать схему аргументов
{
"type": "object",
"properties": {
"plan": {
"enum": [
"solo",
"team",
"scale",
"business"
],
"type": "string",
"description": "Return only this plan. Omit for all plans."
}
},
"additionalProperties": false
}
get_platform_status
Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.
Показать схему аргументов
{
"type": "object",
"properties": {
"service": {
"enum": [
"website",
"api",
"mcp"
],
"type": "string",
"description": "Return only this service. Omit for all services."
}
},
"additionalProperties": false
}
search_docs
Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.
Показать схему аргументов
{
"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
}
list_skills
List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.
Показать схему аргументов
{
"type": "object",
"properties": {
"tag": {
"type": "string",
"description": "Filter skills by tag (e.g. \"backup\", \"restore\", \"schedule\"). Omit for all."
}
},
"additionalProperties": false
}