Filesystem
Gives the AI read/write access to chosen local folders, with path limits you control.
One of the most-installed servers and a default starting point for most setups.
A curated directory of the servers worth installing first. Hand-picked before the long tail.
MCP is the standard that lets an AI use a tool. Think of it as a USB-C port for AI: one shared plug, and any server that speaks it can connect, whether that is your filesystem, your calendar, or GitHub. Instead of every model inventing its own integration, they all speak the same protocol. That is the whole point, and it is why a setup you build today survives the next model swap.
Curated, not searchable. A search box over 49,000 servers is a worse experience for the person this page is for, because they do not yet know what to search for. I picked these because I either use them or I have watched the founders I work with use them. Once you have run two or three and you know what you are missing, the registry search becomes useful. Not before.
Gives the AI read/write access to chosen local folders, with path limits you control.
One of the most-installed servers and a default starting point for most setups.
Reads and writes repos, pull requests, issues, and code search; can trigger workflows.
Official GitHub server, around 31k stars, consistently top of the directory rankings.
Drives a real browser through the accessibility tree, not screenshots: navigate, click, fill forms, extract, test.
Microsoft official, roughly 34k stars (mid-2026), routinely the #1 or #2 server overall.
Injects up-to-date, version-specific docs for 50+ frameworks straight into context.
Upstash, around 58k stars; tops several MCP directories.
Pulls a URL and converts the page to clean Markdown for the model.
A lightweight staple bundled in many default setups.
Exposes Notion pages, databases, and tasks as live context the AI can read and update.
Notion-official server, strong adoption in knowledge-work and PM workflows.
Knowledge-graph memory so an agent recalls facts across sessions.
Official reference server, steady adoption.
Brings production errors and stack traces into the AI so it can diagnose fixes.
Official Sentry remote server, popular with Cursor and Claude Code users for debugging.
Reads channels and posts messages on the AI's behalf.
High interest for team-comms automation; now community-maintained after the reference version was archived.
Tools for payments, customers, and invoices via the Stripe API, plus doc search, over OAuth.
Official remote server, a flagship example of a vendor MCP.
Connects to a Postgres database to run read-only queries, inspect schemas, and list tables.
A very common pattern; the original reference server was archived, the use case lives on through forks and vendor servers like Supabase.
Long tail: for everything not on this list, the Official MCP Registry and the awesome-mcp-servers list stay maintained for you.
Want help wiring these into your own setup?
Join the waiting list