The 6 Best MCP Servers for Claude Code prompt
Install the six best MCP servers for my Claude Code - Context7 (real, current library
docs), GitHub (run my GitHub from the terminal), Supabase (my real database), Sentry (my
real production errors), Vercel (deploys and deploy logs), and Playwright (a real browser
for screenshots). Work in the order below and change nothing until STEP 1.
Safety first: run `claude mcp list` and tell me which of the six already exist. Never
overwrite an existing server - skip any that are already configured. Install everything at
USER scope so it works in every project and no token lands in a file I might commit.
(If a bare `claude ...` command is blocked inside this session, re-run just that command
with CLAUDECODE cleared: `CLAUDECODE= claude ...` on macOS/Linux, or
`$env:CLAUDECODE=''; claude ...` in PowerShell.)
STEP 0 - Ask me which of the six I actually want. If I don't use Supabase, Sentry, or
Vercel, skip those - a server for a service I don't have is just noise. Wait for my answer.
STEP 1 - Install the servers that need no key right now. Playwright is local and needs no
account at all; Supabase, Sentry, and Vercel are hosted and authenticate later with a
browser login:
claude mcp add --scope user playwright -- npx @playwright/mcp@latest
claude mcp add --scope user --transport http supabase https://mcp.supabase.com/mcp
claude mcp add --scope user --transport http sentry https://mcp.sentry.dev/mcp
claude mcp add --scope user --transport http vercel https://mcp.vercel.com
STEP 2 - Context7 needs a free API key. Tell me to open https://context7.com/dashboard,
sign up (free), copy my key, and paste it back here. Then run this with my key in place of
YOUR_KEY:
claude mcp add --scope user --header "CONTEXT7_API_KEY: YOUR_KEY" --transport http context7 https://mcp.context7.com/mcp
STEP 3 - GitHub needs a personal access token. Tell me to open
https://github.com/settings/personal-access-tokens/new, create a FINE-GRAINED token with
Read and Write on "Contents", "Pull requests", and "Issues" for the repos I want managed,
and paste it back here. Treat it as a secret - never print it back in full and never write
it to a file I might commit. Then run this with my token in place of YOUR_GITHUB_PAT:
claude mcp add --scope user --transport http github https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer YOUR_GITHUB_PAT"
If that command errors on Claude Code 2.1.1 or newer, use the JSON form instead (same
server, same token):
claude mcp add-json github '{"type":"http","url":"https://api.githubcopilot.com/mcp/","headers":{"Authorization":"Bearer YOUR_GITHUB_PAT"}}' --scope user
STEP 4 - Restart and authenticate. MCP servers only load at startup, so tell me to fully
quit and reopen Claude Code, then type /mcp and authenticate supabase, sentry, and vercel
with the browser login it offers. Hand this back to me and wait.
VERIFY (after I restart) - run `claude mcp list` and confirm every server I chose shows as
connected. Then prove one works for real: pull the current docs of a library from my
project through Context7, or list my open pull requests through the GitHub server -
read-only, change nothing. Finally, summarize what is installed, what each server lets you
do now, and remind me that everything lives at user scope and any token can be revoked
anytime.Out of the box, Claude Code guesses. It writes code from training data with a cutoff date, guesses what your database schema looks like, guesses why production broke, and guesses what your site actually renders. MCP servers close those gaps by connecting it to the real thing. The catalog has hundreds of servers now, and most are noise. I tested over 20 in real projects and kept six.
Context7 feeds Claude the current documentation of the library you are working with, so it stops writing against APIs that were renamed a year ago. GitHub lets it open and merge pull requests, push branches, and read issues without you ever opening the website. Supabase connects it to your actual database: real schema, real rows, migrations handled for you. Sentry hands it your real production errors, stack trace included, so it fixes the actual bug instead of guessing at one. Vercel lets it deploy your site and read the logs when a deploy fails. And Playwright gives it a browser, so it can load your pages, click around, and screenshot what really renders instead of assuming.
The prompt below installs all six in one paste. It checks what you already have and skips it, asks which of the six you actually use so you don't install servers for services you don't have, and walks you through the only two that need a key. Three of them (Supabase, Sentry, Vercel) just need a browser login after a restart.