By Kodelyth · updated · v2.29.0
Kodelyth ECC — MCP Server
The Kodelyth ECC MCP (Model Context Protocol) server is the universal adapter that lets any MCP-compatible client consume the full ECC stack: 71 agents, 196 skills, 104 commands, 15 rules, 3 power bundles, and the local BM25 self-learning memory.
If you've ever wished LangGraph, AutoGen, CrewAI, OpenAI Agents SDK, Claude Desktop, or any other agent framework could speak ECC natively — this is that bridge.
Local-only, zero telemetry, stdio transport.
Quick start
1. Run the server
# From npm (recommended):
npx kodelyth-ecc mcp
# From this repo:
node scripts/mcp/server.jsThe server speaks JSON-RPC over stdio. It stays alive until stdin closes.
You'll see one stderr banner on boot, e.g.:
[kodelyth-mcp] ready · 2.29.0 · 16 tools · 6 prompts · 389 resources2. Wire it into your MCP client
Auto-wire with --target (recommended)
You usually don't paste any config at all. Installing ECC into an IDE registers this server (and the local memory) for you:
npm i -g kodelyth-ecc
kodelythecc --target cursorThe post-install always registers the server in Claude Code (~/.claude.json) and Claude Desktop, and then wires it into the targeted IDE when it's one of the six ECC can merge safely: claude-code, cursor, windsurf, gemini-cli, codex, and kiro. Five write the standard { mcpServers: { … } } JSON; Codex gets a [mcp_servers."kodelyth-ecc"] TOML table instead. The merge is atomic and refuses to clobber a config it can't parse. Opt out with --no-mcp-register.
Cline and Roo Code keep their MCP settings inside VS Code's globalStorage, a version-specific path ECC won't guess — on those two, paste the entry below by hand.
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS)
{
"mcpServers": {
"kodelyth-ecc": {
"command": "npx",
"args": ["-y", "kodelyth-ecc", "mcp"]
}
}
}Cursor / Windsurf / any MCP-aware IDE
Use the same command + args pattern under whatever the IDE's MCP server config key is.
Programmatic clients (LangGraph, AutoGen, CrewAI, OpenAI Agents SDK, custom)
Spawn the server as a subprocess and connect via the official MCP client SDK for your language. The transport is stdio JSON-RPC — every spec-compliant client supports it.
What it exposes
Tools (16)
| Name | Purpose |
|---|---|
route_intent | Suggest the best ECC agent for a user message via token-overlap. Pair with the routing-rule prompt for full tier-based routing. |
list_agents | List every ECC agent (name, description, relpath). |
list_skills | List every ECC skill. |
list_commands | List every slash command. |
list_rules | List every rule file in rules/common/. |
list_bundles | List the power bundles (indie-hacker, red-team, enterprise). |
get_agent | Fetch the full markdown body of one agent. |
get_skill | Fetch the full markdown body of one skill. |
get_command | Fetch the full markdown body of one slash command (with or without leading /). |
get_rule | Fetch a rule file body. |
get_bundle | Fetch a bundle cheat sheet body. |
recall_memory | BM25 search across the local Kodelyth memory store. |
capture_memory | Append a new memory entry (problem + approach + tags). |
memory_stats | Summary of the local memory store. |
catalog_stats | Summary of how many agents/skills/commands/rules/bundles are loaded. |
audit_skill_match | Suggest skills whose description/body overlap a task — useful for deciding which skills to attach as context. |
All tool results follow the MCP { content: [{ type: 'text', text: ... }], isError? } shape. Most return JSON-encoded payloads inside the text channel.
Prompts (6)
Prompts let clients summon canonical ECC context blocks by name, no tool call needed.
| Name | Returns |
|---|---|
routing-rule | The full ECC intent routing rule (10-tier priority system). |
agents-overview | Compact list of all 71 agents with one-line descriptions. |
skills-overview | Compact list of all 196 skills. |
commands-overview | Compact list of all 104 slash commands. |
handoff-chains | The agent-handoff skill body — standard multi-agent chains for new feature, bug fix, refactor, incident, etc. |
devil-mode | The /devil-mode parallel command — fires the adversarial red-team crew. |
Resources (389)
Every agent, skill, command, rule, and bundle is also addressable as an MCP resource:
kodelyth://agents/<name>
kodelyth://skills/<name>
kodelyth://commands/<name>
kodelyth://rules/<name>
kodelyth://bundles/<name>All resources are text/markdown. Use resources/list to discover, resources/read to fetch.
Example session
// → client
{ "jsonrpc": "2.0", "id": 1, "method": "initialize",
"params": { "protocolVersion": "2024-11-05", "capabilities": {},
"clientInfo": { "name": "my-client", "version": "0.1.0" } } }
// ← server
{ "jsonrpc": "2.0", "id": 1, "result": {
"protocolVersion": "2024-11-05",
"capabilities": { "tools": {}, "resources": {}, "prompts": {} },
"serverInfo": { "name": "kodelyth-ecc", "version": "2.29.0" } } }
// → client
{ "jsonrpc": "2.0", "id": 2, "method": "tools/call",
"params": { "name": "route_intent",
"arguments": { "message": "production is down and i don't know why",
"top_k": 3 } } }
// ← server (paraphrased)
{ "result": { "content": [{ "type": "text", "text":
"{ \"suggestions\": [
{ \"agent\": \"incident-commander\", ... },
{ \"agent\": \"debug-detective\", ... },
{ \"agent\": \"silent-failure-hunter\", ... }
] }" }] } }Design notes
- Pure file reads + memory passthrough. The server adds no LLM calls of its own. It surfaces ECC context; your client's model decides what to do with it.
- No telemetry, no network egress. stdio only. Local memory only. Reads from this repo's checked-in markdown.
- Lazy SDK load. The MCP SDK is an
optionalDependencyso installs work without it; themcpsubcommand prints a friendly install hint if missing. - Cached catalog. Agent/skill/command lists are cached in-process after first read for sub-millisecond subsequent calls.
- Memory store is project-aware.
recall_memoryaccepts an optionalproject_rootto scope BM25 results to memories captured against that project, falling back to global memories if scoped results are sparse.
Privacy & safety
- The server only reads files under this package and the local memory directory (default
~/.kodelythecc/memory/, override viaKODELYTH_MEMORY_DIR). - It writes only when the client invokes
capture_memory. - No network calls. No analytics. No phone-home.
- The server never executes arbitrary commands or code. Tools that surface code (
get_agent, etc.) return markdown documentation, not executable instructions.
Troubleshooting
"Kodelyth MCP server requires @modelcontextprotocol/sdk" — run npm install @modelcontextprotocol/sdk once, or rerun via npx -y kodelyth-ecc mcp to let npm fetch optional deps.
Empty results from recall_memory on a fresh memory store — BM25 needs a few documents before IDF scores rise above the default minScore floor. Capture 2-3 memories first.
Resources missing in your client UI — some MCP clients render only tools and prompts. Resources are still queryable via resources/list.
Related
- External MCP Servers — the inverse direction: ECC consuming external MCP servers (Stripe, GitHub, Postgres, Brave, etc.), making ECC the MCP hub, not just a node. Shipped.
- Dashboard — localhost observability across Memory, RTK, Terse, Codebase, Evolve, Catalog, and Sessions. Shipped.
- Six IDEs, one MCP server — the auto-wiring story, which config file each IDE gets, and why the merge refuses to clobber.
Built into Kodelyth ECC. MIT licensed. PRs welcome.