Copied!
Blog

10 MCP servers that turn Claude Code from clever into unfair

Claude Code is good on its own. With the right MCP servers it can read your live site, check current docs, query your database and open its own pull requests.

← Blog
Lines of colorful code on a dark monitor
Photo on Unsplash

September 29, 2026

MCP servers for Claude Code

Claude Code already reads your files and runs your commands. What it can’t do alone is see anything outside the repo: your deployed site, the docs for the version you’re on, the database, the production errors.

Adding a server is one command:

claude mcp add --transport http enrichr https://enrichr.dev/mcp   --header "X-API-Key: your-key-here"

That’s the setup. The real decision is which servers earn a place, because each one adds to what Claude can (and might) do. Here’s the ten we’d reach for, in rough order of how often we use them.

Disclosure, up front: we build Enrichr, so it appears on this list. We’ve tried to say exactly why, and to be straight about where the others are the better tool.

In this list
  1. *Enrichr
  2. GitHub
  3. Context7
  4. Playwright
  5. Chrome DevTools
  6. Supabase
  7. Sentry
  8. Vercel
  9. Linear
  10. Sequential Thinking

01 Enrichrour pick

Claude Code is great at building; it’s blind to how a target site behaves in a browser. Enrichr closes that gap. Point it at a URL and Claude gets the rendered DOM, design tokens, animation timings, shaders and assets, plus a rebuild_brief written to be built from. It’s the difference between “make it look like that site” and actually being able to.

02 GitHub

Issues, PRs, code search, review comments. Let Claude read the ticket it’s fixing and the discussion behind it.

03 Context7

Fresh docs for the exact library version. It quietly eliminates a whole class of “that API doesn’t exist” loops.

04 Playwright

Lets Claude verify its own work in a browser: click through the flow it just built and confirm it works before declaring victory.

05 Chrome DevTools

Performance traces, network and console, straight from Google. Ask “why is this slow” and get a measured answer.

06 Supabase

Schema inspection, queries and migrations against a real project. Point it at a dev database, never production, until you’re comfortable.

07 Sentry

Turn a production error into a fix: Claude reads the stack trace and the release and goes to the code.

08 Vercel

Deployments, build logs, runtime errors. “Why did the last deploy fail?” becomes a question Claude answers in one step.

09 Linear

Read the ticket, update the status, link the PR. It closes the loop between the work and the tracker.

10 Sequential Thinking

A small reference server that gives Claude a structured scratchpad for stepping through hard problems. Optional, but useful for gnarly refactors.

Watch your tool list. Every server adds tool descriptions to Claude’s context, and a crowded list can make it pick the wrong tool. Ten is a ceiling, not a target. Run /mcp occasionally and remove what you don’t use.