#MCP Servers

Eko uses Model Context Protocol (MCP) servers to give Claude Code live access to project systems — databases, queues, and documentation — without leaving the conversation.

#Registered Servers

Server	Type	Purpose	Guide
eko-admin	Custom (stdio)	Pac-Man progression analytics, simulation, and bulk operations	eko-admin.md
docs-reel	Filesystem (stdio)	Browse and edit Reel video app documentation	docs-reel.md

#Configuration

MCP servers are registered in .mcp.json at the monorepo root (project-scoped) or in user-level Claude settings (user-scoped).

#Project-Scoped (.mcp.json)

{
  "mcpServers": {
    "eko-admin": {
      "type": "stdio",
      "command": "bun",
      "args": ["run", "packages/mcp-admin/src/server.ts"]
    }
  }
}

#User-Scoped

The docs-reel server is configured in user-level Claude settings since it points to a local path outside this monorepo (~/code/reel/docs).

#How MCP Tools Appear in Claude Code

MCP tools are prefixed with mcp__<server>__<tool>:

mcp__eko-admin__progression_status
mcp__docs-reel__read_text_file

Claude Code automatically discovers registered servers on startup. Tools are deferred-loaded — they appear by name but their full schemas are fetched on first use.