State of MCP Servers
A data-driven snapshot of the Model Context Protocol ecosystem, computed from the 520 servers tracked in this directory. Updated August 1, 2026.
Transport
Most servers still run locally over stdio; remote servers (SSE/HTTP) are easier to share but need a hosted endpoint.
Authentication
No-auth servers are the fastest to try — no key to provision first.
Tools per server
6,882 tools across 520 servers — median 10, average 13.2, and the busiest single server exposes 94. Most are thin CRUD wrappers — the six commonest verbs:
Run five average servers and you're near Cursor's ~40-tool budget — check totals with the Config Doctor.
Top categories
Implementation language
Most-starred servers
- 1MarkItDown MCPFiles & Storage★ 162,161
- 2Fetch (Reference)Search & Web★ 87,182
- 3Filesystem (Reference)Files & Storage★ 74,000
- 4Memory (Knowledge Graph)AI, Data & Knowledge★ 74,000
- 5Git (Reference)Files & Storage★ 74,000
- 6Sequential ThinkingAI, Data & Knowledge★ 62,000
- 7OpenMemory MCPAI, Data & Knowledge★ 59,874
- 8Chrome DevTools MCPBrowser Automation★ 44,881
- 9GitHub MCP ServerDevOps & Cloud★ 30,600
- 10Graphiti MCPAI, Data & Knowledge★ 28,240
- 11Context7 MCP ServerDeveloper Tools★ 28,000
- 12Task Master AIProductivity★ 27,705
Download the dataset
Every figure here is computed live from the 520 servers in this directory. Grab the raw data as CSV — one row per server, with transport, auth, official/verified flags, GitHub stars and tool count.
Method & citation
Data is crawled from each server's GitHub repository and refreshed regularly. Official means the repository belongs to the vendor whose product the server wraps — a strict first-party bar, not just a name match. Verified means the docs carry a runnable config and example. Tool counts are the real tools each server exposes.
Citations welcome. Cite as: “State of MCP Servers, mcptrove.com/report (updated August 1, 2026).” Or browse all servers and build a config.