MCP Servers

MCP Overview

EGC runs two local MCP servers over stdio. Both ship prebuilt inside the npm package and are registered by egc init and the installers in the ten tools that take MCP config; every other tool reaches the same memory through the protocol files.

egc-memory

Persistent project memory

working_memory_list

compress_observations

egc-guardian

Validation and safety layer

Transport

Both servers communicate over stdio. Each AI tool spawns them as child processes when a session starts. No daemon, no ports, no network exposure.

// mcp.json as written by egc init (Cursor shown; Claude Code is registered through its own CLI)
{
  "mcpServers": {
    "egc-memory": {
      "command": "node",
      "args": ["<npm global prefix>/node_modules/@egchq/egc/mcp/servers/egc-memory/build/index.js"]
    },
    "egc-guardian": {
      "command": "node",
      "args": ["<npm global prefix>/node_modules/@egchq/egc/mcp/servers/egc-guardian/build/index.js"]
    }
  }
}

Local-first

🔒

No cloud

All state stays on your machine. Nothing is sent to external servers.

📁

Yours to read

State is Markdown, encrypted at rest and owned by the server: egc export prints it decrypted, and deleting a state file resets that project.

⚡

Fast startup

Stdio transport means near-zero latency. Both servers start in under 100ms.