Discovery
All entries

Collection · 16 entries

MCP servers and Model Context Protocol tools

Production MCP servers, gateways, frameworks, and clients - everything in this directory that speaks the Model Context Protocol.

MCP went from spec to ecosystem fast. The tools here split into a few clear shapes: servers that expose data or actions to agents (Prometheus, Figma, codebase intelligence), gateways and aggregators that consolidate many servers behind one endpoint (1mcp), clients and CLIs that let you call MCP tools from a shell (mcpc, mcp2cli), frameworks for building production servers (Golf), and benchmarks for stress-testing them (MCPMark).

If you're new to MCP and want a starting point, look at the codebase intelligence ones (Qartez, codebase-memory-mcp) - they're the most concrete demonstration of what an MCP server actually changes about the agent loop.

Frequently asked

What is the Model Context Protocol?

MCP is an open protocol from Anthropic that standardizes how LLM applications connect to external data sources and tools. An MCP server exposes capabilities (read data, run commands) that any MCP-aware client can call without per-integration glue code.

Do I need to build my own MCP server?

Often no - start with existing servers (codebase intelligence, Prometheus, Figma) and aggregators (1mcp). Build your own when you have proprietary data or a domain-specific action that no off-the-shelf server covers.

How do I evaluate which MCP server actually helps my agent?

MCPMark benchmarks server-and-model pairs on real-world tasks. For your own setup, the practical signal is whether the server reduces tool-call rounds or context bloat versus a baseline of grep/curl.

Related collections