Best MCP servers for Claude Code: choose by task, not hype

Selection criteria

A server appears here only when its primary documentation and source are attributable to the protocol project or the vendor whose service it connects to. The ordering is by common development workflow, not a performance ranking.

These checks do not constitute a security audit. Before installing anything, inspect the current repository, dependencies, requested permissions, release history, and data path.

What the labels mean

• Official protocol documentation: published by the Model Context Protocol project. This explains MCP; it does not endorse every listed server.
• Reference: example implementation in the official modelcontextprotocol/servers repository. That repository explicitly says reference servers are educational examples rather than production-ready solutions.
• Vendor: published by the organization responsible for the connected product or platform. “Vendor” does not mean official to Anthropic or to the MCP project.
• Community: independent implementation. Community status is not a quality judgment, but it requires separate publisher and maintenance verification.

Vendor-maintained shortlist

Reference servers: useful for learning, not a production shortlist

The official MCP servers repository includes reference implementations such as Everything, Fetch, Filesystem, Git, Memory, and Sequential Thinking. They are useful for understanding protocol features and testing a host implementation.

The repository's own warning matters: reference servers are intended to demonstrate MCP features and SDK usage, not to be production-ready. For production use, look for a maintained implementation with a security model and support posture suitable for your environment.

Official MCP reference servers repository

How to handle community servers

This page does not name a community “winner.” A directory listing can help discovery, but it is not an endorsement and can become stale. Evaluate an independent server from first principles:

1. Confirm the publisher identity and source repository.
2. Read the code path that handles credentials and external requests.
3. Check open issues, release provenance, dependency policy, and security reporting instructions.
4. Test with least-privilege credentials and non-sensitive data.
5. Pin and review changes according to your dependency policy.

The official MCP site links to an MCP Registry for discovery. Registry presence should be treated as metadata, not a substitute for due diligence.

Install through Claude Code's documented workflow

Once you have chosen a server, follow its publisher's current instructions and Anthropic's transport-specific claude mcp add guidance. Use project, local, or user scope intentionally. Then run claude mcp list and inspect /mcp inside Claude Code.

Do not copy a stale one-line install command from an unrelated roundup. Endpoints, package names, authentication methods, and required arguments can change independently.

The best default is a minimal set

Each connected server adds another trust relationship and another set of tools Claude may invoke. Prefer one server for the current job, narrow its permissions, and remove or disable it when it is no longer needed. Convenience should not erase provenance or access review.