Claude Code MCP Servers: The Complete Setup Directory

Last verified: October 2026. Every command in the linked guides was run on a real Claude Code install and checked against the vendor’s official docs.

This is the index for every MCP server guide on Quick Prompt Co. Each one connects Claude Code to a tool you already use, so it can read the real thing (your issues, your schema, your rendered page) instead of whatever you paste into the chat. Pick the section that matches what you keep copying by hand.

New to MCP? Start Here

Every server below is added with the same command, claude mcp add. Remote servers take a URL; local ones take the command that starts them. How to connect any MCP server to Claude Code covers both, plus scopes and troubleshooting, in about 2 minutes.

Want a first set that needs no account? 5 MCP servers with no account and no API key installs docs, search, page reading, and two browser servers in one paste, with the context each one costs.

Connecting a database? Read-only Supabase, Neon, and MongoDB shows the one-line read-only setup for each and what the switch removes.

• Remote (HTTP): nothing to install. Claude Code connects to the vendor’s hosted server, and you sign in through /mcp when it asks.
• Local: Claude Code starts the server on your machine with npx, uvx, or Docker. Needs Node.js, uv, or Docker installed.
• Scope: --scope user makes a server available in every project; --scope project writes it to .mcp.json so your team gets it too.

Compare Every Server Side by Side

All 21 single-server guides in one table. Type a tool or a job (“logs”, “SQL”, “issues”), narrow by how it runs and how it signs in, or tap a column header to sort.

Browse by What You Need

Code, issues, and errors

Stop pasting tickets, diffs, and stack traces. These give Claude Code the context your team already tracks.

Server	What Claude Code gets	Runs	Sign-in
GitHub	Issues, pull requests, and CI status for your repos	Remote (HTTP)	Personal access token
Linear	Read issues first, then create and update them	Remote (HTTP)	OAuth
Atlassian (Jira + Confluence)	Jira issues and Confluence pages, with your own permissions	Remote (HTTP)	OAuth
Sentry	Production errors, breadcrumbs, and Seer root-cause analysis	Remote (HTTP)	OAuth
Vercel	Deployments, build and runtime logs, and protected previews	Remote (HTTP)	OAuth
Cloudflare	DNS, Workers, cache, and analytics through the whole API in two tools	Remote (HTTP)	OAuth

Browser and web

Claude Code’s built-in WebFetch reads static HTML. These let it search, render JavaScript, and drive a real browser.

Server	What Claude Code gets	Runs	Sign-in
Playwright	Opens a real browser, clicks through flows, fills forms	Local (npx)	None
Chrome DevTools	Console errors, network requests, performance traces	Local (npx)	None
Firecrawl	JavaScript-rendered scraping, search, and PDF parsing	Remote (HTTP)	None (keyless endpoint)
Exa	AI-native web search and URL-to-Markdown fetch	Remote (HTTP)	None to start

Docs and code intelligence

Fewer outdated suggestions and fewer tokens spent reading whole files.

Server	What Claude Code gets	Runs	Sign-in
Context7	Current, version-matched library documentation	Remote (HTTP)	None to start
Shopify Dev	shopify.dev search, current API schemas, validator for GraphQL and Liquid	Local (npx)	None
Serena	Find symbol, references, and rename across 40+ languages	Local (uvx)	None

Design and knowledge

Give Claude Code the source of truth instead of a screenshot or a pasted spec.

Server	What Claude Code gets	Runs	Sign-in
Figma	Real layout, variables, and components	Remote (HTTP)	OAuth
Notion	Pages and databases from your workspace	Remote (HTTP)	OAuth

Data, payments, and monitoring

Start these read-only or in a sandbox. Each guide shows the safe first setup.

Server	What Claude Code gets	Runs	Sign-in
Supabase	Tables, SQL, logs, and generated types, scoped to one project	Remote (HTTP)	OAuth
Neon	Schema, SQL, and 15 Postgres health checks, read-only by URL flag	Remote (HTTP)	OAuth
MongoDB	Find, aggregate, schema, and explain plans on local or Atlas, read-only by flag	Local (npx)	Connection string
Stripe	Products, prices, and payments, starting in a sandbox	Remote (HTTP)	OAuth
Grafana	Dashboards, PromQL and LogQL queries, and alerts	Local (uvx)	Service account token
Database roundup	Postgres, Supabase, Redis, MongoDB, and ClickHouse options compared	Varies	Varies

Running many servers

Once you have more than a handful, manage them in one place.

Server	What Claude Code gets	Runs	Sign-in
Docker MCP Gateway	Runs servers in isolated containers behind one Claude Code entry	Local (Docker)	Per server
Community picks	Five community servers that passed a 2026 maintenance check	Varies	Varies

Which Ones to Install First

Don’t install everything. Each connected server adds its tools to Claude Code’s context, and a long tool list makes it slower to pick the right one. A good starting set for most developers:

1. Context7 for current library docs. It fixes the most common kind of wrong answer.
2. Whichever issue tracker your team uses: GitHub, Linear, or Jira.
3. Playwright or Chrome DevTools if you build anything for the web.

Add the rest when you catch yourself pasting the same kind of thing into the chat for the third time.

Keep It Safe

• Read-only first. Linear, Supabase, and Grafana all have read-only setups. Start there and widen access once you trust the workflow.
• Sandbox anything with money or production data. The Stripe guide starts in a sandbox for this reason.
• Prefer official servers. Every guide here uses the vendor’s own server where one exists. For community servers, check maintenance first; our 2026 check shows how.

Beyond MCP

MCP gives Claude Code access to tools. Two other features decide how it behaves:

• Skills: instructions that load themselves when a task matches, so you stop re-explaining conventions.
• Hooks: commands that always run on certain events, like formatting every edit or blocking dangerous shell commands.