MCP server

SecondOS speaks the Model Context Protocol, so any MCP-capable AI tool reads your codebase map through one interface. One sync, one growing toolset, every editor.

How it fits together

You sync a repo with the CLI. The map and embeddings live in the cloud (or your self-hosted instance). The MCP server exposes that map to your tools. Nothing re-scans your repo per tool, and nothing re-explains context per session.

your repo → CLI push → map + vectors
                          │
                    MCP server
        ┌─────────────┼─────────────┐
     Cursor      Claude Code     Copilot

The tools

Every connected tool gets the same surface. The core codebase tools:

• project_overview — A structure-aware summary of the repo: what it is, its shape and its entry points.
• search_codebase — Hybrid lexical + semantic search over the map, including symbol bodies when deep-synced.
• recent_activity — What changed recently, from git re-entry — so a tool starts where the last one left off.
• who_uses — Callers of a symbol, ranked by confidence (exact, resolved, heuristic).
• impact_of — Blast radius of a change: what will break vs what might break.
• schema_drift — Columns your code writes that the database schema does not have — a read-only alert.

Plus memory tools (remember, recall, and history / rollback / reconcile so an agent curates its own notes) and an action layer (list_action_tools + run_action_tool — one surface over every connected integration, writes gated by preview then confirm).

Connecting a tool

Add the SecondOS MCP server to your tool's MCP configuration. In most editors that is a small JSON entry pointing at the server command:

{
  "mcpServers": {
    "secondos": {
      "command": "bunx",
      "args": ["@secondos/cli", "mcp"]
    }
  }
}

Once connected, the tool can call any of these tools above against your synced map. If your tool supports it, memory writes go through the same protocol, so notes are validated and bound to real symbols.

Privacy note

The MCP server serves the map, never your source — because the source was never uploaded in the first place. See security for the full boundary.

Next

Head to the CLI reference for sync options, or back to the quickstart.