The Best MCP Servers for Claude Code
The best MCP servers for Claude Code I actually run, how local and free options differ, and the one security check before install.
The best MCP servers for Claude Code are the ones you actually use every week, not the twenty you installed and forgot.
I have cycled through more than thirty of them across Claude Code and Cursor. Most got uninstalled within a week. MCP, the Model Context Protocol, is how these tools reach outside the chat window. The protocol is fixed. The servers built on it are not, and quality varies a lot. MCP is one of several features worth learning in Claude Code, but it is the one most people get wrong first, usually by installing too many at once.
This is the shortlist I would actually recommend, how local servers differ from free ones, and the one check I run before adding anything new.
The best MCP servers for Claude Code I actually run
Five servers cover almost everything I do in a normal week.
github for pull requests, issues, and code search without leaving the terminal. If you install one MCP server first, make it this one.
context7 pulls current library docs into context instead of relying on stale training data. This is the single server that cut my "wrong API version" bugs to almost zero.
playwright lets Claude open the deployed site, click through it, and take screenshots. It checks its own work instead of me asking it to "please verify".
supabase, or postgres if you are not on Supabase, gives Claude direct SQL and schema access from chat. No more pasting table definitions by hand.
sentry pulls production errors straight into the conversation, so triage starts with a real stack trace instead of a vague bug report.
None of these are exotic picks. They are the ones I open every day, which is a better filter than "sounds interesting". This list overlaps almost exactly with my full harness setup, because a good MCP list does not change much once you find it.
Local MCP server vs remote: what to pick
Every MCP server runs one of two ways: local or remote.
A local MCP server runs as a subprocess on your machine, talking over stdin and stdout. Claude Code starts it, uses it, and shuts it down with the session. There is no network hop and nothing to expose.
Use a local MCP server for anything touching your filesystem, a database socket, or a browser you want Claude to see. Claude Code's MCP docs show the actual syntax: claude mcp add --transport stdio my-db -- npx -y @modelcontextprotocol/server-postgres postgresql://localhost:5432/mydb. That one line is the whole setup.
A remote MCP server runs as a hosted service instead. You connect over HTTP, often through OAuth, the same way you authorize any third-party app. GitHub's remote server and most SaaS integrations work this way now.
The trade-off is simple. Local servers are faster and everything stays on your machine. Remote servers need zero setup on your end, but you are trusting someone else's infrastructure with your session.
In my experience, filesystem, database, and browser tools stay local. Team tools like Slack, Linear, and Notion are almost always remote, because the vendor already runs the server for you.
Best MCP servers for Cursor
Cursor speaks the same protocol, so most of the list above works unchanged.
The difference is a ceiling. Cursor caps out around 40 active tools across every MCP server you have enabled combined. Go past it and the agent starts silently losing access to tools, with just a warning buried in the logs.
So the best MCP servers for Cursor are not automatically the same five I use in Claude Code. They are the four or five that matter most for the repo you are actually in.
For a typical web app, that usually means GitHub, Postgres, Playwright, and one search tool like Brave Search or Firecrawl. Drop the rest until you need them.
Cursor improved this in January 2026, when a dynamic context update cut token usage by close to 47 percent when running several MCP servers at once. It still adds up fast. I stay closer to five servers than fifteen, on either tool.
Free MCP servers worth installing
Nearly everything on this list is free.
github, context7, playwright, and DuckDuckGo's search server all run on open source code with no subscription attached. You install a free MCP server with npx and there is nothing to buy.
A free server still costs you something: setup time, and the review time to trust the code before you run it. Neither is a wallet cost, which is why free is the default here, not the exception.
The registries have grown fast this year. Glama alone lists over 50,000 open source servers. Most of those are someone's weekend project, so free does not mean vetted. Check the GitHub stars and the last commit date before you install anything obscure.
The security check before you install one
MCP servers run with your permissions. A bad one is not a bug, it is a foothold.
OWASP now lists tool poisoning as an MCP-specific risk, where a server's tool descriptions look normal but its responses carry hidden instructions the model follows without asking you.
One 2025 audit of popular MCP servers found 43 percent had command-injection flaws and 30 percent were exploitable through server-side request forgery, mostly because authentication was off by default.
Before I install anything outside the well-known five, I check three things. Who maintains it, is the source code public, and does it ask for more access than the job requires. A weather server does not need my GitHub token.
If a server wants broad filesystem or shell access, I run it in a sandbox first, never in a repo with production secrets attached.
Where to start
Do not install fifteen servers on day one.
Start with github and one more for whatever you touch most: context7 if you write against fast-moving libraries, playwright if you ship anything with a UI. For a longer list beyond these five, the wider GitHub ecosystem has more MCP servers, skills, and hooks worth knowing.
Run claude mcp list after each addition to confirm it connected. Use it for a week before adding the next one. If you have not opened a server in a month, remove it.
That is the actual filter. Not a static "best MCP servers for Claude Code" list somebody wrote in January, but the ones still active in your claude mcp list output ninety days from now.