KödMCP¶

KödMCP lets an agent CLI use the project memory in KödMem without sending that memory through a hosted service. The bundled kodade-mcp server runs as a local stdio process and reads the local KödMem database directly.

What the server does¶

An MCP client launches kodade-mcp for a registered project. The server can return STATE.md with recent worklog entries, checkpoints, decisions, tasks, and full-text memory searches. With permission, it can also create, revise, or delete typed memories, record checkpoints, and report that a session needs your attention.

The server works while the ködade desktop UI is closed. It opens no network port and requires no token or other shared secret. Its trust boundary is the local executable and your operating-system user account.

KödMCP is deliberately local stdio only. Remote MCP transport is not included.

Connect agents safely¶

KödMem's Connect agents section prepares a configuration change for supported clients. For Claude Code it targets a project .mcp.json; for Codex it targets ~/.codex/config.toml.

Before writing, the setup flow detects the existing configuration, prepares a single-entry merge, and shows the diff. It makes a backup, applies the merge, verifies it, and can restore the backup. Existing MCP servers remain intact. This is the same safety discipline used by KödHarness: it never replaces a whole third-party configuration file.

Keep memory scoped and visible¶

Each connection is scoped to a project already registered in ködade. A client cannot select an arbitrary filesystem path through an MCP request. You can make a connection read-only, revoke it, review recent reads and writes, export memory, or delete its records from the app.

Every memory mutation records its source and timestamp. KödMem does not automatically capture raw terminal or KödChat transcripts and guards against oversized or likely credential-bearing writes. Read Köd Workspace and KödMem for what the local files and database contain, and security boundaries for the separate permissions of the terminal and agent CLI.