← mitosislabs.ai

INDIVIDUAL MCP TOOL

get_platform_status

Get the operational status of the Mitosis website, API, and MCP server.

mitosislabs.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mitosislabs.ai/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_platform_status and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • A tool name or description suggests retrieving external content.

Parent server

mitosislabs.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mitosis]
url = "https://mitosislabs.ai/api/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: mitosis
Remote MCP URL: https://mitosislabs.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mitosis": {
      "type": "http",
      "url": "https://mitosislabs.ai/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mitosis",
  "transport": "streamable-http",
  "url": "https://mitosislabs.ai/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • 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.
  • cortex_recall — Semantic-only vector search over the memory, returning source excerpts.
  • 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.
  • cortex_status — Memory health: per-source ingest and embed counts plus last sync times.
  • 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.
  • cortex_connect_link — The connect link for one memory source, by id — email and calendar (google-workspace), WhatsApp chats, GitHub, Notion, or file uploads.
  • cortex_remember — Persist a fact, decision or conclusion into the memory, attributed to you.
  • 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.