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: 70 agents, 194 skills, 97 commands, 14 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.js

The 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 · 1.7.0 · 16 tools · 6 prompts · 365 resources

2. Wire it into your MCP client

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)

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.

Resources (365)

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": "1.7.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 optionalDependency so installs work without it; the mcp subcommand 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_memory accepts an optional project_root to 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 ~/.kodelyth/memory/, override via KODELYTH_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.

Roadmap interactions

• Phase 2.5 — MCP client mode will add the inverse: ECC agents consuming external MCP servers (Stripe, GitHub, Postgres, Brave, etc.) — making ECC the MCP hub, not just a node.
• Phase 2.3 — local dashboard will visualize live MCP traffic so you can see which tools/prompts/resources clients hit, in real time.
• Phase 2.10 — prompt-injection guardrail will sit in front of MCP responses to scrub jailbreak patterns before they reach client models.

Built into Kodelyth ECC. MIT licensed. PRs welcome.