5 MCP Servers Every Claude Code Developer Should Set Up

You’re debugging a production issue. You need to check the related GitHub PR, search for a Stack Overflow answer, and read an API doc — all at the same time. With plain Claude Code, you spend half your time copy-pasting between browser tabs. With MCP servers, Claude does it all without leaving your terminal.

That’s the promise of MCP. Here are the 5 servers that make it real.

What Is MCP?

Model Context Protocol is an open standard that lets Claude Code connect to external tools and data sources. Think of it as USB ports for your AI assistant — each MCP server is a peripheral that gives Claude a new capability.

The result: Claude stops being a code editor and starts being a connected development environment.

How to Add MCP Servers

Two transport types. Choose based on where the server runs:

# Remote servers (hosted on the web)
claude mcp add --transport http <name> <url>

# Local servers (run on your machine via npx/binary)
claude mcp add --transport stdio [--env KEY=val] <name> -- <command> [args...]

Key things to know:

Options come before the server name
-- separates the server name from the command that runs it
Default scope is local (current project only). Use --scope user for all projects.

# Check what you have installed
claude mcp list

# Remove a server
claude mcp remove <name>

# Inside an active session, check status
/mcp

Now let’s set them up.

1. GitHub MCP — Manage PRs and Issues Without Leaving Terminal

What it does: Create PRs, review issues, search code, manage repos — all through Claude Code. No browser tab switching.

Install:

claude mcp add --transport http github https://api.githubcopilot.com/mcp/

Authenticate: Start a Claude Code session, then run /mcp. It will prompt you to authenticate with GitHub.

Use case: You’re writing a fix and want Claude to check if there’s already an open issue for it, then create a PR with the right labels once you’re done. With GitHub MCP, that’s a single conversation.

Important: The old @modelcontextprotocol/server-github npm package is archived. Use this remote server instead.

2. Brave Search MCP — Web Search That Actually Works

What it does: Real-time web search inside Claude Code. Find documentation, check Stack Overflow, look up current package versions.

Prerequisites: Free API key from brave.com/search/api. The free tier gives you 2,000 queries/month — plenty for development use.

Install:

claude mcp add --transport stdio \
  --env BRAVE_API_KEY=YOUR_KEY \
  brave-search -- \
  npx -y @brave/brave-search-mcp-server

Replace YOUR_KEY with your actual Brave Search API key.

Use case: You’re implementing OAuth and want Claude to search for current best practices. Instead of pausing to Google it, Claude searches directly and incorporates the results into its response.

Important: The old @modelcontextprotocol/server-brave-search is archived. Use @brave/brave-search-mcp-server from Brave directly.

3. Playwright MCP — Browser Automation Built In

What it does: Control a real browser from Claude Code. Take screenshots, fill forms, run E2E tests, scrape content. Microsoft maintains this one.

Install:

claude mcp add --transport stdio playwright -- npx -y @playwright/mcp@latest

No API keys needed.

Use case: You’ve built a form and want to verify it actually works end-to-end. Ask Claude to open the browser, fill in the fields, submit, and screenshot the result. Done in one prompt — no manual testing, no writing a test script first.

Also useful for debugging visual issues. “Screenshot what my login page looks like on mobile” is a valid prompt when Playwright MCP is connected.

4. Filesystem MCP — Controlled Access Outside Your Project

What it does: Gives Claude read/write access to directories you specify. Claude Code already has access to your project directory — this server extends that to other paths on your system.

Install:

claude mcp add --transport stdio filesystem -- \
  npx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir

Replace /path/to/allowed/dir with the actual path. You can specify multiple directories by adding more paths at the end.

Use case: Your project reads config files from ~/configs/ or writes output to ~/Documents/reports/. Claude needs to read those files to help you debug. Without Filesystem MCP, you’d have to copy-paste file contents manually. With it, Claude reads them directly.

Keep the allowed paths narrow. Don’t grant access to your entire home directory — give it only what Claude needs.

5. Fetch MCP — Pull Web Content Into Your Conversation

What it does: Fetch any URL and convert it to clean, readable markdown. Great for pulling in documentation, reading changelogs, or analyzing web content.

Install:

claude mcp add --transport stdio fetch -- npx -y @modelcontextprotocol/server-fetch

Use case: You’re integrating a third-party API and the docs are on a website, not in your codebase. Ask Claude to fetch the docs page and write the integration based on what it reads. No copy-pasting, no context window stuffing.

Also useful for: reading release notes before upgrading a package, pulling in spec sheets, or grabbing any reference material that lives on the web.

Cheat Sheet

Server	Transport	Install Command	Best For
GitHub	HTTP	`claude mcp add --transport http github https://api.githubcopilot.com/mcp/`	PRs, issues, code search
Brave Search	stdio	`claude mcp add --transport stdio --env BRAVE_API_KEY=KEY brave-search -- npx -y @brave/brave-search-mcp-server`	Web search, docs lookup
Playwright	stdio	`claude mcp add --transport stdio playwright -- npx -y @playwright/mcp@latest`	Browser automation, screenshots
Filesystem	stdio	`claude mcp add --transport stdio filesystem -- npx -y @modelcontextprotocol/server-filesystem /your/path`	Files outside project dir
Fetch	stdio	`claude mcp add --transport stdio fetch -- npx -y @modelcontextprotocol/server-fetch`	Fetch URLs as markdown

Watch Out for Archived Packages

The MCP ecosystem moves fast. A lot of the original @modelcontextprotocol/ npm packages have been archived — including the ones for GitHub, Brave Search, PostgreSQL, SQLite, and Puppeteer.

Before installing any MCP server, check the official MCP servers repository for the current maintained version. The archived packages still install, but they won’t receive updates or bug fixes.

The 5 servers in this guide are current as of March 2026.

Start Simple, Add as You Go

Don’t install all 5 at once. Start with the two you’ll use most:

Working heavily with GitHub? Add GitHub MCP first.
Constantly searching for docs? Add Brave Search first.

Once those feel natural, add the rest. Each server you add makes Claude Code more capable — but only if you actually use it.

These 5 servers cover 80% of what you’ll reach for daily. Web search, GitHub, browser control, file access, URL fetching. Once they’re set up, Claude Code stops being a smart text editor and starts being a connected development environment that reaches across your entire stack.

That’s the shift worth making.