# MCP server

SecondOS speaks the Model Context Protocol, so any MCP-capable AI tool reads your codebase map through one interface. Twenty-two tools:

**Codebase (10):** project_overview, search_codebase, recent_activity, who_uses, impact_of, schema_drift, schema_timeline, schema_at, cross_repo_drift, symbol_detail.
**Memory (7):** remember, recall, capture_decision, ingest_issues, memory_history, restore_memory, reconcile_memories.
**Context (5):** get_context_pack, read_doc, read_living_doc, what_changed_since, prime (a memory-first orientation call that hands a new agent the index before it asks).

Two of these pull knowledge in from where decisions get made: `ingest_issues` distils a repo's issue and pull-request discussions into reviewable proposals (opt-in, read-only, human-accepted; a PR-sourced note binds to the file it touched so it goes stale by drift), and `read_living_doc` serves the map-derived living docs straight into an agent (read-only, free).

Local (stdio): `secondos mcp <path>` — free, runs on your machine. Hosted (HTTP): a project-scoped token + `https://secondos.app/mcp` for agents that can't spawn a process (claude.ai, ChatGPT) — Pro. Run `secondos mcp-config` to print ready-to-paste config for Cursor, Claude Code, Windsurf, VS Code.