The best MCP servers are the ones teams actually call every day, not the ones mounted and forgotten. This is a short, opinionated list of the best MCP servers grouped by category, plus a thesis worth restating: the best MCP server is the one written against an internal API. Everything else is a fallback. A twenty-line wrapper around an internal billing system saves more time than any polished SaaS server. Build first, install second. The MCP catalog is for the gaps that cannot be filled in-house.

The list below covers the best MCP servers across dev tools, knowledge, productivity, finance, and hardware, along with the categories worth uninstalling.

GitHub by github. The daily driver. Read PRs, comment, open issues. Tool descriptions are decent and the auth flow is sane.

Filesystem by Anthropic. Boring, essential. Read, write, glob. Pair it with a sandbox and stop worrying.

Playwright by Microsoft. Browser automation that returns accessibility trees instead of pixels. Use the MCP for UI work, the CLI for fetch-and-parse.

Docker Hub by Docker. Search images, read tags, pull metadata. Replaces typing docker search ever again.

Context7 by Upstash. Library docs at version-pinned granularity. Agents stop hallucinating function signatures. This one earns its slot among the best MCP servers for code generation.

Octocode by bgauryy. Reads code across repos the way grep handles a laptop. Useful for vendor audits.

Slack by korotovsky. The community fork covers thread metadata and reactions the official one skipped. See the earlier note on official servers for context on why community forks exist.

Notion. Search, read, draft. The write side is still rough, but the read side replaces five tabs.

Linear. Issue triage from inside a chat. Filter by project, update status, assign. The closest thing to "agent acting as a PM" that works today.

Stripe. Reads only. Pull a customer record, check a subscription. Write access is not yet trustworthy, and the same caution applies broadly.

Home Assistant by community. Real, and surprisingly useful. Lights, thermostat, door locks. One user wired an espresso machine to this server. The future is dumber and more fun than predicted.

Kubernetes by Flux159. Read pods, describe deployments, tail logs. Read-only is the only mode that should exist in prod.

A few categories get recommended often but rarely survive a week of real use. Generic "web search" servers (modern models already search well). Most database servers with write access (too easy to drop a table on a bad prompt). Anything that wraps a SaaS in fifteen tools instead of three (tool-selection accuracy tanks).

This list of the best MCP servers gets refreshed quarterly. The MCP ecosystem moves fast enough that half of these picks will read differently by August. The thesis holds: the best MCP server remains the one built in-house, and the catalog covers the rest.