Top 5 MCP Servers for Claude Code (Configs Included)
· Insights
The 5 MCP servers that turn Claude Code into a full dev team — GitHub, Playwright, codebase-memory-mcp, filesystem, and Context7. Full configs included.
Last updated: September 3, 2025 · 8-minute read
I added one MCP server to Claude Code and watched it go from "smart terminal assistant" to "I just created a PR, wrote the tests, and updated the docs without asking me." That one server was GitHub. I've since added four more, and the difference in daily workflow is the single biggest productivity shift I've had since switching from VS Code to Cursor.
Builder.io published a roundup called "The Best MCP Servers for Developers in 2026" that listed 12+ servers. Reddit's r/ClaudeAI has a sticky thread "Must-Have MCP Servers for Coding and Beyond" with community picks. Both are useful lists. This is not another list — it's the 5 I actually run daily, with real config files and honest opinions on where each one breaks.
What MCP Actually Does (Briefly)
MCP — Model Context Protocol — is Anthropic's open standard for connecting AI assistants to external tools. An MCP server is a small program that exposes capabilities (read files, query a database, control a browser) through a standardized interface that Claude Code, Cursor, Windsurf, and any compliant client can consume.
One server, multiple clients. Unlike plugins or extensions, MCP servers are client-agnostic. Write once, use everywhere.
The key insight from Anthropic's own engineering blog on code execution with MCP: the protocol lets agents handle more tools while using fewer tokens. Instead of pasting API documentation into your prompt, the agent queries the tool directly.
1. GitHub MCP Server — Version Control Without Context Switching
What it does: Lets Claude Code create branches, open PRs, review diffs, manage issues, and trigger CI — all from the terminal.
Why it matters: I used to have three windows open — terminal (Claude Code), browser (GitHub), and editor (Cursor). The GitHub MCP server killed the browser window. When Claude Code finishes a feature, I say "create a branch, commit, and open a PR." It does it. No alt-tabbing.
Setup:
Generate a PAT at GitHub Settings → Developer Settings → Personal Access Tokens → Fine-grained. Grant repo permissions (read/write for code, read for PRs and issues).
Where it breaks: Large diffs. When a PR touches 50+ files, the MCP server struggles to return the full diff within Claude's context window. I've had it truncate changes and miss files in big PRs. For those, I still review in the browser.
Reddit sentiment: The r/ClaudeAI thread calls it a time-saver that "eliminates context switching between your environment and GitHub." The r/ClaudeCode community ranks it as the #1 must-have MCP server in their 2026 list.
2. Playwright MCP — Browser Automation for Testing and Scraping
What it does: Gives Claude Code a real browser. It can navigate pages, click elements, fill forms, take screenshots, and extract content.
Why it matters: I covered AI testing in the TestSprite post — Playwright MCP is the layer below that. It's the raw browser control that lets Claude Code do things like "open my app, log in, take a screenshot of the dashboard, and tell me if the layout looks right."
Setup:
One command. No API keys. Microsoft maintains the official server at github.com/microsoft/playwright-mcp.
Where it breaks: Speed. Browser automation is slow compared to direct API calls. A r/ClaudeAI thread on Claude + Playwright noted that "the browser is slow to start up and each action takes a few seconds." It's fine for testing and occasional scraping — not for anything that needs to run fast or at scale.
Real use case: I asked Claude Code to "check if the pricing page on my site loads correctly and the Stripe integration is working." It opened the page, filled out the test card details, submitted, and confirmed the checkout flow. That's a 2-minute task that would have taken me 10 minutes of manual clicking.
3. codebase-memory-mcp — The Map Your Agent Needs
What it does: Indexes your codebase into a persistent knowledge graph using tree-sitter. Instead of grep-ing your whole repo or relying on file paths, Claude Code can query the graph for structural information — "where is authentication handled?" or "what components use the User type?"
Why it matters: This is the Week 2 callback. I wrote about Claude Code memory and codebase setup earlier — codebase-memory-mcp is the next evolution. The GitHub repo (DeusData/codebase-memory-mcp) describes it as a "high-performance code intelligence MCP server" that indexes codebases in milliseconds.
The core problem it solves: Claude Code either reads your entire repo (expensive, token-heavy) or guesses which files to read (inaccurate). Codebase-memory-mcp gives it a structural map. A dev.to article titled "Stop Making Your AI Coding Agent Grep Your Whole Repo" explains that it parses your code with tree-sitter and builds a graph — the agent queries the graph instead of scanning files.
Setup:
Run /codebase-memory index in Claude Code to build the initial graph. Subsequent queries hit the persisted database.
Where it breaks: Claude doesn't automatically use it. A GitHub issue titled "Claude never uses codebase-memory-mcp unless I explicitly tell it to" is the most upvoted issue on the repo. You need to add instructions in CLAUDE.md: "Before answering codebase questions, query the codebase-memory MCP server." Without that nudge, Claude falls back to grep.
4. Filesystem MCP — Beyond the Project Directory
What it does: Gives Claude Code read/write access to your local filesystem beyond the current project directory.
Why it matters: Claude Code is sandboxed to your project by default. The filesystem MCP server lets it read config files, access shared libraries, write output to any directory, and reference documentation stored elsewhere on your machine.
Setup:
Where it breaks: Security. You're giving an AI agent write access to your filesystem. Be specific about which directories you expose. I limit it to my projects folder and nothing else.
Honest take: This is the least exciting of the five but the one I'd miss most if it was gone. It removes the "I can't access that file" friction that kills agent workflows mid-task.