Best MCP Servers for Claude Code (With Setup Commands)
The best MCP servers for Claude Code are the ones that remove copy-paste from your day: GitHub (issues and PRs), Context7 (current library docs), Playwright (a real browser to test your UI), your database server (Supabase or Neon), and your deploy and error tools (Vercel, Sentry). Start with two or three, not ten. Every server adds tools to the agent's context. Below, each pick has the setup command from the vendor's own docs or Anthropic's MCP guide, checked on 17 October 2026. For the wider catalogue of open-source servers and CLIs, see our agent tools directory.
New to the protocol? Read MCP explained first. Using Cursor instead? We have a separate list of the best MCP servers for Cursor.
The top picks at a glance
| # | Tool | Best for |
|---|---|---|
| 1 | GitHub MCP Server | Issues, pull requests and repo context |
| 2 | Context7 | Up-to-date library documentation |
| 3 | Playwright MCP | A real browser for testing your UI |
| 4 | Supabase MCP | Your Postgres database, auth and edge functions |
| 5 | Neon MCP Server | Serverless Postgres with branches |
| 6 | Vercel MCP | Deployments, build logs and docs |
| 7 | Sentry MCP | Real production errors and stack traces |
| 8 | Notion MCP | Specs and docs from the source |
| 9 | Stripe MCP | Payments work in test mode |
How MCP works in Claude Code (60-second version)
Claude Code connects to MCP servers in three ways, per its docs:
- Remote HTTP server (recommended for cloud services):
claude mcp add --transport http <name> <url> - Local stdio server (runs on your machine):
claude mcp add <name> -- <command> [args...]. Everything after--goes to the server untouched. - JSON copied from another client:
claude mcp add-json <name> '<json>'
Manage them with claude mcp list, claude mcp get <name>, claude mcp remove <name>, and /mcp inside a session (which is also where you sign in to OAuth servers).
Where the config lives (scopes)
| Scope | Flag | Loads in | Shared with team | Stored in |
|---|---|---|---|---|
| Local (default) | --scope local |
Current project only | No | ~/.claude.json |
| Project | --scope project |
Current project only | Yes, commit it | .mcp.json in project root |
| User | --scope user |
All your projects | No | ~/.claude.json |
Claude Code asks for approval before it uses project-scoped servers from a .mcp.json file in an interactive session, and a cloned repo cannot approve its own servers until you trust the folder.
The best MCP servers for Claude Code
1. GitHub MCP Server: issues, pull requests and repo context
GitHub's official server lets Claude read issues, review PRs and open new ones, so "implement issue 42" works without pasting. Anthropic's docs show the remote setup with a fine-grained personal access token:
claude mcp add --transport http github https://api.githubcopilot.com/mcp/ \
--header "Authorization: Bearer YOUR_GITHUB_PAT"
Safety: scope the token to the repos you need and start read-only. GitHub's install guide for Claude also covers a local Docker option.
2. Context7: up-to-date library documentation
Models learn from a snapshot, so they can suggest outdated APIs. Context7 pulls current, version-specific docs into the prompt. Its README recommends a one-command setup that can target Claude Code:
npx ctx7 setup --claude
Manual alternative: the server URL is https://mcp.context7.com/mcp with your key in an Authorization: Bearer header (a free key raises rate limits). Add "use context7" to prompts, or a line in CLAUDE.md.
3. Playwright MCP: a real browser for testing your UI
Microsoft's Playwright server lets Claude open your local app, click through it and read the page via accessibility snapshots, which closes the loop on front-end bugs. From the README:
claude mcp add playwright npx @playwright/mcp@latest
Safety: point it at localhost or staging. Web pages can carry text written to manipulate the model.
4. Supabase MCP: your Postgres database, auth and edge functions
If your backend is Supabase, its hosted server lets Claude list tables, run SQL, apply migrations and read logs. From Supabase's docs:
claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp"
Then run /mcp, select supabase and authenticate. Safety: Supabase recommends scoping to one project and read-only mode; append ?project_ref=YOUR_REF&read_only=true to the URL. Never connect it to production data you can't afford to leak.
5. Neon MCP Server: serverless Postgres with branches
On Neon? Its README offers a one-command setup that works with Claude Code (OAuth, creates an API key and configures the client):
npx neon@latest init
The managed server lives at https://mcp.neon.tech/mcp. Neon branches are a safe sandbox for agent-written migrations (see Neon vs Supabase).
6. Vercel MCP: deployments, build logs and docs
Vercel's official remote server lets Claude search Vercel docs, manage projects, inspect deployments and read logs. From the Vercel MCP docs:
claude mcp add --transport http vercel https://mcp.vercel.com
Then /mcp to sign in. Vercel says the connection gets the same access as your Vercel account, so keep human confirmation on. Pair it with our guide on how to deploy a vibe-coded app.
7. Sentry MCP: real production errors and stack traces
With Sentry connected, Claude can read the actual error, find the code and propose a fix. Anthropic uses it as its OAuth example:
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Run /mcp (or claude mcp login sentry) to authenticate in the browser.
8. Notion MCP: specs and docs from the source
If your product specs live in Notion, connect them instead of summarising them for the agent. From Anthropic's docs:
claude mcp add --transport http notion https://mcp.notion.com/mcp
9. Stripe MCP: payments work in test mode
Building checkout? Stripe's server (shown in Anthropic's scope examples) lets Claude look up products, prices and payment links:
claude mcp add --transport http stripe https://mcp.stripe.com
Safety: authorise a test-mode account first, and keep approvals on for anything that creates or refunds.
Starter stacks by project
| You are building | Install these first |
|---|---|
| A solo web app (Next.js + Supabase) | GitHub, Context7, Playwright, Supabase (read-only) |
| A SaaS on Vercel + Neon | GitHub, Context7, Neon, Vercel, Sentry |
| A team product with specs in Notion | GitHub, Notion, Sentry, your database (read-only) |
| Generic Postgres, no vendor server | DBHub (below) with a read-only user |
For a generic Postgres, MySQL or similar database, Anthropic's docs show DBHub with a read-only connection string:
claude mcp add --transport stdio db -- npx -y @bytebase/dbhub \
--dsn "postgresql://readonly:pass@localhost:5432/mydb"
Keep MCP fast and safe in Claude Code
- Fewer servers, better answers. Each server adds tools and context. Enable per project with
--scope projectinstead of loading everything globally. - Watch output size. Claude Code warns when one MCP tool result exceeds 10,000 tokens and caps it at 25,000 by default (
MAX_MCP_OUTPUT_TOKENSchanges the cap). - Least privilege. Read-only database users, scoped tokens, test-mode payment keys.
- Keep secrets out of git. In a committed
.mcp.json, reference${ENV_VAR}instead of pasting tokens; Claude Code expands variables at load time. - Treat fetched content as untrusted. Anthropic warns that servers fetching external content expose you to prompt injection. Only install servers you trust.
- Tell the agent when to use them. One line in
CLAUDE.md("Use the Supabase MCP server to check the schema before writing SQL") helps a lot. See prompt tips for coding agents.
How we picked
We chose servers that are maintained by the vendor (or, for Playwright, by Microsoft) and that fix a common vibe-coder pain point: missing context (GitHub, Notion, Context7), no way to verify (Playwright), or blind backend work (database, deploy logs, errors). Every command was copied from the vendor's README/docs or Anthropic's Claude Code MCP page on 17 October 2026. We did not include community servers that need broad account access. Commands change, so if one fails, check the linked source first.
Sources
- Connect Claude Code to tools via MCP (Anthropic)
- GitHub MCP Server: install guide for Claude
- Context7 README (Upstash)
- Playwright MCP README (Microsoft)
- Supabase MCP Server docs
- Neon MCP Server README
- Vercel MCP docs
How we ranked these tools
Rankings are editorial and never sold; sponsored placements are always labelled. We rank each tool for the specific job named in its heading, using what the tool's own website, docs and pricing page state. Pricing notes reflect the official pricing page at the time of writing (17 Oct 2026); prices and plans change, so confirm on the official site before you buy. Read more about how AIUseFlow ranks tools.
FAQ
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http <name> <url> for a remote server or claude mcp add <name> -- <command> for a local one, then type /mcp in Claude Code to check the status and sign in if needed.
Where is the Claude Code MCP config file?
Project-shared servers live in .mcp.json at the project root; local and user-scoped servers are stored in ~/.claude.json in your home directory.
How do I list my MCP servers in Claude Code?
Run claude mcp list in your terminal to see every configured server with a health status, or /mcp inside a session for details and authentication.
Which MCP server should I install first?
For most people building web apps, GitHub plus Context7 gives the biggest immediate gain; add Playwright for front-end work and your database server (read-only) next.
Are MCP servers safe to use with Claude Code?
They are as safe as their code and the permissions you give them. Use official servers, scoped or read-only credentials, keep tool approvals on, and treat web pages and issue text as untrusted input.
See the full ranking: best Coding agents tools, ranked.