MCP Servers
MCP Overview
EGC runs two local MCP servers over stdio. Both are compiled from TypeScript and installed to your machine.
egc-memory
Persistent project memory
get_state update_state store_decision query_history search_history working_memory_set working_memory_get working_memory_list lesson_save lesson_recall lesson_reinforce detect_patterns compress_observations get_project_state egc-guardian
Validation and safety layer
validate_command validate_write reduce_context orchestrate_task 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 (Claude Code / Cursor)
{
"mcpServers": {
"egc-memory": {
"command": "node",
"args": ["/home/user/.egc/servers/egc-memory/dist/index.js"]
},
"egc-guardian": {
"command": "node",
"args": ["/home/user/.egc/servers/egc-guardian/dist/index.js"]
}
}
}Local-first
🔒
No cloud
All state stays on your machine. Nothing is sent to external servers.
📁
Plain files
State is Markdown. You can read, edit, or delete it with any text editor.
⚡
Fast startup
Stdio transport means near-zero latency. Both servers start in under 100ms.