MCP Servers for Claude Code
Claude Code keeps its servers in its own config, managed by claude mcp add. Of the 54 394 we track, 20 798 answer right now without any credentials, 8 428 sign you in through the browser and 3 298 want an API key you paste into the config. The blocks below are ready to paste — each is built from the address we actually reached, in the format this client expects.
What 54 394 servers look like from Claude Code
How to add a server to Claude Code
three scopes: this project, this user, or shared through a file in the repositoryOne command, no file to open. For a remote server pass its address and transport; for a local one pass the command that launches it.
claude mcp add <name> --transport http <url>Lists everything the current scope knows about, with the transport of each.
claude mcp listA server that answers with a challenge instead of its tool list needs credentials. Roughly a quarter of remote servers behave this way, and it means they are running, not broken.
What it looks like
a real server, not a placeholderrun in your terminal
Browser Use →
claude mcp add browser-use --transport http https://api.browser-use.com/v3/mcpServers to start with
all 54 394 in the catalogue →Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Playwright Tools for MCP
Gives AI development tools Firebase-specific capabilities and expertise.
Help agents automatically write and test stories for your UI components.
Up-to-date docs for AI agents
MCP server for Chrome DevTools
Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
AI marketing agent and AI ad generator: 1178 tools, usable alone. No model markup on Starter and up.
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Official TypeScript library for the Telnyx API
Open live web and mobile app sessions from an e2e project to inspect the app and try locators.
Things that trip people up with Claude Code
Written from how Claude Code reads its config, not from its release notes.
Where does the server end up?
Why does the command form differ per server?
The server was added but no tools showed up
How many servers should be connected at once?
Can the same server be used in another project?
Is it safe to add a server that asks for a key?
Same servers, other clients
the servers are the same — the config format is notEditor with the agent built in. Takes stdio, streamable HTTP and SSE, and can carry an OAuth login for each of the three.
Autonomous agent living inside VS Code. Handles local processes and remote endpoints over streamable HTTP or SSE, but authorisation is on you — through headers or environment variables.
Google's command-line agent. Takes all three transports and carries a full OAuth flow for remote servers, including service-account impersonation.
Built into the JetBrains IDEs. Configured through the settings dialog rather than a file, and it can import a config you already wrote for another client.
Open-source terminal agent. Local and remote servers sit in the same mcp object, told apart by a type field, and tokens are kept outside the config.
Config sits in the project folder, so servers can differ per repository — useful when one project needs database access and another must not have it.
Works through GitHub Copilot's agent mode. Like Cursor, the config is per workspace rather than global.
The only client here that uses TOML rather than JSON, so a config copied from elsewhere will not work as is.
One global config for everything, so a server added here is available in every conversation. The file starts local servers; remote ones are added in the app under Settings → Connectors.