Mitosis

安装

选择你使用的 AI 应用，然后复制设置。

通过 2/3 项检查 · 你的提问会经过开发者的服务器（mitosislabs.ai） · ✓ 命令已检查 2026年11月13日

claude mcp add --transport http --scope user mitosis https://mitosislabs.ai/api/mcp

{
  "mcpServers": {
    "mitosis": {
      "url": "https://mitosislabs.ai/api/mcp"
    }
  }
}

{
  "servers": {
    "mitosis": {
      "type": "http",
      "url": "https://mitosislabs.ai/api/mcp"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月10日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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, docu

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

• 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

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

• 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

• 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

• 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

• 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

• 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

• 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 alo

• 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, beca

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

• 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 p

• 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

• 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, decisi

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

• audiograph_open_link

  Open an Audiograph link someone shared (https://audiograph.si/a/...) for the person you are working with, and read it: the recorded conversation’s transcript, its notes (summary, action items, decisions) and the people and places mentioned. Works for one Audiograph, several sent

• audiograph_list_received

  List the Audiographs (recorded conversations) other people have sent the person you are working with: who sent each, its title, date and length. Read one with audiograph_read_received.

• audiograph_read_received

  Read one Audiograph someone sent the person you are working with: transcript, notes and who was mentioned. recording_id comes from audiograph_list_received.

• audiograph_task_report

  Tell your person how a to-do they handed you from Audiograph is going. Use the report URL and token from the brief. status: "started" when you begin, "working" with a short step, "needs_you" with the question when you need an answer (their phone is notified), "done" with result.s

• get_pricing

  Get current Mitosis plans, prices, credit allowances, how usage is charged, and add-ons. Use when comparing costs or recommending a plan.

• get_platform_status

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

• search_docs

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

• list_skills

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

• ! 注意

  作者与仓库一致

  发布者（mitosislabs.ai）不是仓库所有者（OperatingSystem-1）；可能是其他人代为上架的

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 210 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 24 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

• 星标数多于此分类中其他 6115 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 6115 个服务器的 21% 更新
• 基础检查结果等于或优于此分类中其他 6115 个服务器的 50%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

Up-to-date docs for AI agents

作者：upstash·广泛使用·↓ 125万/周·★ 6.5万·前天更新

电脑或云端

安装

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

作者：DeusData·广泛使用·↓ 1.7万/周·★ 4.9万·28天前更新

在你的电脑上运行

安装

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者：every-app·广泛使用·★ 2.8万·今天更新

在云端运行✓ everyapp.com

接入方法

作者的 README

仓库中没有找到 README