feat: add MCP server for dynamic agent discovery

[kienbui1995]

What

Adds an MCP (Model Context Protocol) server that exposes all 106 agents dynamically — any MCP-compatible client can browse, search, and use agents without running install scripts or copying files.

Why

Currently, using agents requires running convert.sh + install.sh and copying files to specific tool directories. An MCP server lets any compatible client (Claude Desktop, Kiro CLI, VS Code, Cursor) discover and use agents with zero setup beyond pointing to the server.

Tools

Tool	Description	Example
list_agents	List all agents, filter by division	list_agents(division: "engineering") → 16 agents
get_agent	Get full agent prompt by name	get_agent(name: "Frontend Developer") → full prompt
search_agents	Keyword search across name/description/content	search_agents(query: "React") → 14 results

Setup

cd mcp-server && npm install && npm run build

Then add to any MCP client config:

{
  "mcpServers": {
    "agency-agents": {
      "command": "node",
      "args": ["/path/to/agency-agents/mcp-server/build/index.js"]
    }
  }
}

Test Results

list_agents()                        → 106 agent(s)
list_agents(division: "engineering") → 16 agent(s)
get_agent(name: "Frontend Developer") → full prompt with identity, mission, rules
search_agents(query: "React")        → 14 result(s)
search_agents(query: "security")     → matches across divisions

Tech

• TypeScript + @modelcontextprotocol/sdk v1.x
• stdio transport (standard for local MCP servers)
• Reads agent .md files directly from repo (no pre-processing needed)
• 5 files, 299 lines total

Files

mcp-server/
├── src/index.ts      # Server implementation (154 lines)
├── package.json
├── tsconfig.json
└── README.md         # Setup docs for Claude Desktop, Kiro, VS Code, Cursor

[msitarzewski]

Hey @kienbui1995 — this is a genuinely useful idea, but it's a poor fit for this repo. Adding an MCP server introduces npm, TypeScript compilation, and a dependency tree into what is otherwise a pure-markdown project. Contributor simplicity is sacred here — adding an agent is one markdown file.

I'd love to see this as a standalone package that reads from a cloned agency-agents repo. You could publish it as @agency-agents/mcp-server or similar. Happy to link to it from our README once it's published!

Your other PRs (#154, #155, #157) are excellent — this one is just a scope mismatch. Keep them coming!