Directory
MCP Server List 2026: The Definitive Directory of Every Server Worth Using
A curated directory of 34 MCP-compatible servers, grouped by category. Every entry is a server that an actual production agent loop has depended on — not a GitHub link someone skimmed once. If a server is on this list, it earned a place through an 8-dimension review.
Search for "mcp server list" in 2026 and you get two flavors of answer: raw GitHub awesome-lists with 400 dead links, or marketing pages that pretend every new server is a breakthrough. Neither is useful when you are trying to actually ship an agent.
This is a third option. We maintain the ToolRoute registry, a living catalog of tools that AI agents use through a single API gateway. Every server here is scored on capability, protocol support, cost, maturity, resale potential, reliability, ecosystem, and agent-native design. Servers are only listed if they clear rating 9 or 10 on that scale. Everything below that line gets demoted quietly.
Curation methodology
Three things make this list different from the average awesome-mcp repo:
- 8-dimension scoring. Every server gets rated 1 to 10 on eight axes. A new entry has to beat the incumbent on 5 of 8 to take a category slot. Hype alone does not move the rankings.
- Real usage telemetry. The registry powers a production MCP gateway. Every call we route feeds back into reliability and latency scores. Tools that fail in production fall off the list, even if they look great on paper.
- Category champions. We do not dump 400 servers on you. We pick winners. If two servers do the same thing, only the one that won is listed — unless the loser has a specific edge case worth documenting.
The list below is the output of that process as of April 2026. It is organized by super-category so you can jump to the layer you care about. For a narrative version of the same data focused on individual champions, see Best MCP Servers for AI Agents in 2026.
What qualifies as an MCP server
Every entry below speaks the Model Context Protocol natively — the JSON-RPC spec Anthropic open-sourced in late 2024 that has since become the default integration surface for agent frameworks. Most also expose a REST or OpenAPI surface for backward compatibility, but the MCP interface is what gets them on this list. If a tool has only a REST API and no MCP server, it lives elsewhere in the registry and is not part of this directory.
Infrastructure (7)
The bedrock layer — databases, auth, browser control, docs, and the plumbing agents lean on most.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Supabase MCP mcp / rest / openapi | Full Supabase backend in one MCP server: DB, storage, auth, edge functions, migrations, config. | 10/10 | free |
| Playwright MCP mcp | Official Anthropic Playwright MCP. Deterministic browser automation via accessibility snapshots. The standard. | 10/10 | free |
| Composio mcp / rest / openapi | OAuth for 850+ apps. 11K+ tools. Managed auth infrastructure for AI agents. MCP + REST + SDK. | 10/10 | freemium |
| Context7 mcp | Injects live, version-specific documentation into prompts. #1 MCP server. 50.1K GitHub stars. Eliminates doc hallucination. | 10/10 | free |
| Blender MCP mcp | Natural language to 3D scenes in real time. 17K+ stars. 1500 Blender operators simplified to chat. | 9/10 | free |
| Google Stitch mcp / skill | Voice/text to finished UI designs. DESIGN.md export. MCP server. Free 350 gen/mo. Ships CC skills. | 9/10 | free |
| Grafana MCP mcp | 40+ tools across 15 categories. Apache 2.0. 2.6K stars. Observability standard. | 9/10 | free |
DevOps & Deployment (4)
Ship code, manage containers, and run edge infra without leaving the agent loop.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| GitHub MCP mcp | Official GitHub MCP. Repos, PRs, issues, workflows — full integration. 27K stars. | 10/10 | free |
| Vercel MCP mcp / rest | Official Vercel MCP. Access logs, docs, projects, deployments, domains. | 9/10 | freemium |
| Cloudflare MCP mcp / rest | Deploy/configure Workers, KV, R2, D1. Edge computing standard. | 9/10 | free |
| Docker MCP mcp | Container management via MCP. Build, run, manage Docker containers. | 9/10 | free |
Communication (4)
Email, SMS, voice, team chat — the surfaces where agents actually reach humans.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Twilio rest / openapi / mcp | SMS, voice, video, messaging automation. The undisputed standard for communication APIs. | 10/10 | paid |
| Slack API rest / mcp | Send messages, read channels, reply to threads, list channels. | 10/10 | free |
| Slack MCP mcp | Official Slack MCP. 47 tools. Post messages, read channels, manage workflows. | 9/10 | freemium |
| Gmail MCP mcp | Official Gmail MCP via Composio. Read inbox, parse emails, auto-respond across accounts. | 9/10 | free |
CRM & Sales (3)
Where pipeline data lives. Agents read, write, and progress deals without human copy-paste.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| HubSpot CRM rest / mcp | CRM — contacts, deals, pipeline, notes. | 10/10 | freemium |
| HubSpot MCP mcp / rest | CRM management via MCP. Contacts, deals, pipeline, companies, notes. | 9/10 | freemium |
| Smartlead mcp / rest | 116-tool MCP for cold email. Sequences, warmup, tracking, deliverability. | 9/10 | paid |
Content & Creative (2)
AI video, avatars, and generative media. The highest-leverage category for solo operators.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Higgsfield rest / mcp | AI video & image platform — 30+ models (Sora 2, Kling 3.0, Veo 3.1, Soul 2.0, Seedance). 4.5M generations/day. | 10/10 | usage-based |
| HeyGen MCP mcp / rest | AI avatar/spokesperson videos. Talking head explainers. Official MCP. | 9/10 | paid |
Marketing & Growth (2)
Distribution and data — social, scraping, and the tools that push reach beyond a single app.
Finance & Payments (1)
Billing, invoicing, and subscriptions. This is where agents move money, so it has to be exact.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Stripe MCP mcp / rest / openapi | Official Anthropic Stripe integration. Customers, invoices, subscriptions, products, refunds. | 10/10 | freemium |
E-commerce (1)
Storefronts agents can read inventory from and push product updates to.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Shopify MCP mcp / rest / graphql | E-commerce management via MCP. Products, orders, collections, inventory. | 9/10 | freemium |
Operations & Workspace (7)
Docs, sheets, tasks, and the automation glue holding the rest together.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Notion rest / mcp | Workspace — pages, databases, search, knowledge base. | 10/10 | freemium |
| Notion MCP mcp / rest | Official Notion MCP. Pages, databases, blocks. Internal documentation. | 9/10 | freemium |
| Zapier MCP mcp | 30K actions, 8K apps. When nothing else covers it, Zapier does. Long-tail king. | 9/10 | freemium |
| n8n mcp / rest / npm | Self-hostable workflow automation. 1084+ nodes, 2646+ configs. Open source alternative to Zapier. | 9/10 | freemium |
| Google Sheets MCP mcp | Spreadsheet operations via MCP. Create/edit/analyze spreadsheets. | 9/10 | free |
| Google Drive MCP mcp | File storage via MCP. Store/retrieve/share files across accounts. | 9/10 | free |
| Linear MCP mcp / rest / graphql | Issue management and project tracking via MCP. Developer-focused. Clean API. | 9/10 | freemium |
Scheduling (1)
Calendar access is still one of the highest-agency things you can give an agent.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Google Calendar MCP mcp | Official Google Calendar MCP. Create/edit/delete events, check availability. | 9/10 | free |
Security (1)
Static analysis and scanning so agents can audit their own code before it ships.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Semgrep MCP mcp | Code security scanning via MCP. Find vulnerabilities in code. | 9/10 | freemium |
Analytics & Observability (1)
Close the loop. Know when something broke before your customers do.
| Server | What it does | Rating | Cost |
|---|---|---|---|
| Sentry MCP mcp | Zero-install remote MCP. OAuth 2.0. Seer AI root cause analysis. Best error tracking. | 9/10 | freemium |
Observations from running the registry
A few patterns show up every time we refresh this list:
- Official beats community. Whenever Anthropic, GitHub, Stripe, Vercel, or Slack ships a first-party MCP, it almost always dethrones the community server within a quarter. Stripe MCP, GitHub MCP, Playwright MCP, Vercel MCP, and Slack MCP all arrived that way. Community servers still matter for long-tail coverage, but the top of every category eventually goes first-party.
- Most teams need four servers, not forty. The realistic starter stack is something like Supabase (data) + GitHub (code) + Playwright (browser) + one integration hub like Composio or Zapier MCP to cover every other SaaS the agent eventually needs. Everything beyond that is specialization.
- Aggregators cover the long tail. Composio alone maps to 850+ apps and 11K+ tools. Zapier MCP covers 8K apps and 30K actions. For the servers you will hit once a month, aggregators are almost always the right answer — dedicated MCP only wins when you hit the API every day.
- Context7 stays #1 because it solves the base problem. Almost every agent bug we see traces back to outdated API knowledge. Context7 injects current, version-specific docs at prompt time. It is rating 10 because skipping it costs more than installing it.
- Protocol breadth beats protocol purity. The best servers expose MCP plus REST plus (often) OpenAPI. Clients change. Agents change. Servers that support multiple surfaces survive longer.
What to install vs. what to access through a gateway
Every server on this list ships as a standalone MCP binary you can self-install. Most of them take between five and thirty minutes to wire up: install, configure credentials, restart your client, register the tool, then start troubleshooting whatever silent auth failure inevitably surfaces.
Multiply that by the 34 servers in this directory and you have a full-time job. The reason we built ToolRoute was precisely this math. One API key fronts all of them through a single gateway. Authentication, credit billing, rate limiting, retries, and protocol translation all happen upstream. Your agent calls POST /api/v1/execute with the tool slug and arguments, and the response comes back in whatever protocol you asked for — MCP Streamable HTTP, REST, A2A, OpenAI function calling, or a native SDK call.
We still maintain and recommend the standalone servers. If you are building on a long-lived, single-tenant agent where install time is amortized over years of use, hosting them yourself is fine. If you are running a fleet of agents, spinning up ephemeral sessions, or embedding tools into a product where end users bring their own credentials, the gateway pattern almost always wins.
How the list changes month to month
A few things trigger a re-rank:
- A new MCP ships from an official vendor (most common cause of a champion swap).
- A provider kills a server or breaks a major version without a migration path (rarer, but it happens).
- Production usage data contradicts the paper score. A server rated 9 that reliably returns 503s under load will get reviewed and demoted.
- A new super-category emerges. 3D modeling, avatar video, and observability were not meaningful agent categories two years ago. Now they are.
Each change gets logged with a reason. You can see the current state any time at /tools.
FAQ
How many MCP servers are in the ToolRoute registry total?
87 tools across 14 categories, of which 34 expose a native MCP server (the rest are REST-only or SDK-based). This directory lists the MCP-speaking subset. The full registry including REST-only tools lives at /tools.
Do I have to install every server on this list?
No. You can install any of them directly from their own repos, or you can call all of them through a single ToolRoute API key. Both are supported paths.
Why is server X not on the list?
Either it did not clear rating 9, it duplicates a champion in its category without a unique edge, or we have not scored it yet. The registry is open — submit a tool at /tools and it enters the review queue.
How is this different from the official MCP registry?
The official registry is open and comprehensive — every server gets in. This directory is opinionated and curated — only champions get in. Both are useful. Ours is designed for operators who want a short list they can build on today, not a catalog.
One API key. All of them.
You can install all 34 servers above yourself over the next weekend. You will spend most of that weekend on OAuth flows, rate limit retries, and config files. Or you can call every server in this directory through one ToolRoute API key: prepaid credits, MCP Streamable HTTP + REST + A2A + OpenAI Functions from the same endpoint, unified billing, and the same curation you just read.
Start with the four-server stack, graduate to the dozen you actually need, and let the registry keep evolving in the background. That is the whole pitch.
Related reading
This directory updates as the registry evolves. Browse all 34+ MCP servers or grab an API key and call any of them through one gateway.