MCP collections
Curated, editorial slices of the directory. Every collection answers a specific question: "what are the best open-source ones?" "which are fastest to set up?" "which work best for autonomous agents?" Each list is ranked and kept current.
All collections
8 editorial lists covering the most common "which MCP should I pick?" questions.
Best Open-Source MCPs
Open-source MCP servers are where the MCP ecosystem is actually being built. You can read the source, file issues, fork the server to fix a paper cut, and deploy without licensing friction. Everything on this page ships under an OSS license.
Best Fast-Setup MCPs
Not every MCP needs a 30-minute configuration. These ship in under five minutes — a single npx command, no tokens to generate (or at most one), and zero infrastructure to stand up. Perfect for sanity checks, demos, and first-MCP workflows.
Best Agent-Friendly MCPs
MCPs designed with autonomous agents in mind: clear tool schemas, well-named actions, predictable failure modes, and tool descriptions that the model can understand without handholding. These are the servers that actually perform when you loop them inside Claude Code, Cursor Agent, or a custom agent harness.
Builder Favorite MCPs
The MCPs that developers install first and return to most often. These show up in nearly every AI-builder stack we track — the Swiss-Army-knife set. If you are spinning up a new workstation, start here.
Best Official MCPs
Official MCP servers are maintained by the platform or service they wrap. GitHub builds the GitHub MCP. Supabase builds the Supabase MCP. The advantage is simple: new API features land in the official server first, and the maintainer has every incentive to keep the integration working.
Best Lightweight MCPs
Small footprint, few dependencies, fast startup. Lightweight MCPs are perfect for CI pipelines, low-spec dev machines, and anywhere you want to keep the agent sandbox boot time under a second. No bundled Chromium, no 100 MB docker images.
Best Read-Only MCPs
Read-only MCPs can inspect, query, and fetch — but they never write, post, or trigger side effects. That makes them the safest option for exploratory agent workflows, production databases, and anywhere a misfire would cost money or corrupt state.
Best Action-Taking MCPs
Action-taking MCPs cause real effects in external systems: they post messages, create issues, run code, deploy infra, or charge cards. Powerful — and also the class of MCP where approval policy, scoping, and confirmation flows matter most. Pair these with a client that prompts before side-effecting calls.