MCP
The MCP server exposes read-only project memory tools to MCP-capable clients, including coding agents. Use MCP when a client supports structured tools. Use the CLI when a shell command is simpler or when you want direct human-readable output.
stdio server
Run a local stdio MCP server for clients that spawn tools as child processes (Codex, Claude Code, etc.):
codifix mcp run --project <slug>
codifix mcp status --project <slug>Stdio mode writes only MCP JSON-RPC messages to stdout; diagnostics go to stderr.
Streamable HTTP server
The service can expose MCP over a local HTTP route, typically /mcp. Use this
only for local, token-bearing clients unless you add your own network and
authentication controls. In multi-user mode, HTTP MCP accepts a scoped service
token and deliberately ignores browser session cookies.
Tools
The MCP surface is read-first and focused on project context.
| Tool | Purpose |
|---|---|
codifix_query | Ask a project question and return answers with citations. |
codifix_search_all | Search all projects and return project/repository routing metadata for each result. |
codifix_resume | Generate a continuation briefing. |
codifix_up_to_speed | Generate a new-agent briefing. |
codifix_overview | Inspect counts and project state. |
codifix_list_memories | Browse memory rows. |
codifix_get_memory | Inspect one memory. |
codifix_memory_history | Read memory version history. |
codifix_list_activities | Inspect activity events. |
codifix_list_replacement_proposals | Review pending proposals without approving them. |
Use codifix_search_all when an agent can work across several repositories. The result JSON includes project, project_name, and repo_root fields when the service can identify them. After choosing a result, switch to that repository and continue with project-scoped tools or normal code actions.
When a task may belong to any repository, call codifix_search_all first. Use the
project and repo_root metadata from the strongest cited result to choose where
follow-up actions should happen.Security
- Prefer stdio for local desktop or CLI clients.
- Keep Streamable HTTP bound to local interfaces unless you add network controls.
- Require token-bearing clients for HTTP MCP.
- Create the token with
codifix auth token create; store it in the MCP client's secret configuration. - Scope tools to explicit projects.
- Do not expose MCP HTTP to the public internet.
Next
Read Agents, Watchers, or Operations. For Authentik, roles, and service-token setup, read Authentication and access.