13 MCP servers

Why you'd want it

Context7 targets outdated training data and hallucinated APIs by fetching documentation and code examples for the library and version you name in the prompt. Its MCP server has two tools: resolve-library-id maps a library name to a Context7 ID, and query-docs returns docs relevant to a question. It can also run without MCP as the ctx7 CLI plus an agent skill, and npx ctx7 setup configures either mode for Cursor, Claude Code or OpenCode.

Best for

• Coding agents working with fast-moving libraries
• Pinning answers to a specific library version
• Cursor and Claude Code users

Use it when

Your agent keeps writing code against outdated or nonexistent APIs for the libraries you depend on.

Why you'd want it

MCP is the protocol behind every server in this category: a server exposes tools, resources and prompts once, and any MCP client, such as Claude, ChatGPT, VS Code or Cursor, can discover and call them. Messages are JSON-RPC 2.0 over stdio for local servers or Streamable HTTP for remote ones, with OAuth recommended for remote auth. Official SDKs cover TypeScript, Python, C#, Go, Rust, Ruby, Java, Swift, PHP and Kotlin, so you can build a server or client in the language you already use.

Best for

• Exposing your own API or data to AI clients
• Building an agent host that connects to many servers
• Standardizing tool integrations across clients

Use it when

You want agents to reach an internal system or service, or you are building a client that should plug into existing MCP servers.

Why you'd want it

Microsoft's MCP server exposes Playwright browser automation as tools that act on structured accessibility snapshots, so no vision model is needed and actions avoid the ambiguity of screenshot-based clicking. It runs Chrome, Firefox, WebKit or Edge, headed or headless, can attach to your logged-in browser through the Playwright extension, and has opt-in capabilities for network, storage, DevTools, PDF, vision and test assertions. The README positions MCP for long-running loops that need persistent browser state, and points coding agents to the more token-efficient Playwright CLI with skills.

Best for

• Exploratory web automation by agents
• Self-healing tests and long-running browser workflows
• MCP clients without built-in browser control

Use it when

Your agent needs to navigate, fill forms and inspect pages across many steps while keeping the same browser session.

Why you'd want it

It gives an agent the parts of Chrome DevTools a developer reaches for: recording performance traces with extracted insights, inspecting network requests, reading console messages with source-mapped stack traces and taking screenshots. Automation runs on Puppeteer and waits for action results automatically. A --slim mode trims the tool set for basic browser tasks, and a separate CLI works without MCP.

Best for

• Debugging front-end bugs with an agent
• Performance analysis of web pages
• Checking console and network errors after a code change

Use it when

You want your coding agent to check its changes in a real Chrome instance, reading console, network and performance data the way you would in DevTools.

Why you'd want it

GitHub's official MCP server lets an agent browse and search code, manage issues and pull requests, monitor Actions runs and review code scanning and Dependabot alerts. GitHub hosts a remote version at api.githubcopilot.com/mcp with OAuth or personal access token auth, and the same server runs locally from a Docker image or a Go binary. Tools are grouped into toolsets you can enable selectively, and a read-only mode removes every tool that makes changes.

Best for

• Agents that triage issues or review pull requests
• Investigating CI failures from the editor
• Teams that want a hosted server with OAuth

Use it when

Your agent needs to read or act on GitHub repositories, issues, pull requests or workflows as part of its task.

Why you'd want it

The server exposes Firecrawl scrape, map, crawl, search, parse, interact and agent tools, plus monitors for recurring page checks and a credit usage tool. A hosted endpoint works keyless for scrape, search and parse within rate limits, and signing in or adding an API key unlocks the full tool set. You can also run it locally with npx or Docker and point it at a self-hosted Firecrawl API with FIRECRAWL_API_URL.

Best for

• Turning URLs into clean markdown or schema-shaped JSON
• Crawling many pages under one site
• Pages that need a click before they can be read

Use it when

Your agent needs content from known URLs, a whole site or a search query, in a format it can read directly.

Why you'd want it

Supabase hosts the server at mcp.supabase.com, so most clients need only the URL and an OAuth login to reach your projects. Tools are grouped into features (database, debugging, development, Edge Functions, account, docs, branching, storage) that you can restrict, and you can scope the server to one project or run it in read-only mode, where SQL runs as a read-only Postgres user. The npm package also exports tool schemas for the Vercel AI SDK MCP client and a handler for serving the tools from your own endpoint.

Best for

• Apps built on Supabase
• Letting a coding agent inspect schemas and apply migrations
• Debugging with project logs and advisors

Use it when

Your app runs on Supabase and you want the agent to read schemas, run SQL, apply migrations or check logs from your editor.

Why you'd want it

The reference fetch server from the MCP project. Its single fetch tool converts HTML to markdown, truncates long pages and takes a start_index so the model can continue reading where it stopped, with a raw option for unconverted content. By default it obeys robots.txt for model-initiated requests and refuses private, loopback and cloud metadata addresses; flags let you set the user agent, use a proxy or allow private IPs.

Best for

• Adding web page reading to a client that lacks it
• Reading docs and articles as markdown
• Python or uv-based setups

Use it when

Your agent needs to read web pages by URL and your client has no built-in web fetch tool.

Why you'd want it

The reference filesystem server from the MCP project, published on npm as @modelcontextprotocol/server-filesystem. Access is limited to allowed directories passed on the command line or supplied by the client through MCP Roots, which can change at runtime without a restart. Every tool carries read-only, idempotent and destructive hints, so clients can tell a directory listing apart from an overwrite.

Best for

• Giving Claude Desktop or another chat client local file access
• Scoped file access for agents without built-in file tools
• Learning how an MCP server is built

Use it when

Your MCP client has no file access of its own and you want to grant it specific directories, optionally read-only through a Docker mount.

Why you'd want it

Paste a Figma link into your agent's chat and the server fetches that design's metadata from the Figma API, then simplifies it to the layout and styling information before handing it to the model. The author's case is that this reduced, structured context lets the model implement designs more accurately than pasting screenshots. It runs locally through npx with your own Figma access token.

Best for

• Implementing Figma designs in code
• Cursor users
• Front-end work from design handoff

Use it when

You build UI from Figma designs and want the agent to read the actual file data instead of a screenshot.

Why you'd want it

Stripe hosts an MCP server at mcp.stripe.com with OAuth; its tools search, inspect, read and write Stripe API methods and search the Stripe docs, which makes much of the API reachable without loading every endpoint into context. Stripe requires human confirmation before some write actions, such as refunds and outbound payments. The stripe/ai repo also holds the Agent Toolkit for Python and TypeScript (OpenAI Agents SDK, LangChain, CrewAI, Vercel AI SDK), a local MCP package, billing integrations for the Vercel AI SDK and native OpenAI, Anthropic and Gemini SDKs, and Stripe agent skills and plugins.

Best for

• Products built on Stripe
• Agent frameworks that need Stripe tools via function calling
• Looking up Stripe docs while integrating

Use it when

You build on Stripe and want a coding agent or your own agent to query and change Stripe objects, or to answer integration questions from the Stripe docs.

Why you'd want it

Exa hosts the server at mcp.exa.ai/mcp and it works without an API key under rate limits, so setup is a URL or a plugin install. The default tools are web_search_exa, which returns clean content for search results, and web_fetch_exa, which reads pages as markdown; advanced search with domain and date filters and Exa Agent runs for multi-step research can be turned on with the tools URL parameter. The repo also ships search and exa-agent skills that load with plugin installs.

Best for

• Coding agents that need current web results
• Multi-step research and list-building
• Improving built-in web search in Claude, ChatGPT or Codex

Use it when

Your agent needs to search the web or read pages as clean markdown and you want a hosted server with nothing to install.

Why you'd want it

Sentry runs a remote MCP server at mcp.sentry.dev that uses OAuth and acts as middleware to the Sentry API, with tools chosen for debugging workflows in coding assistants rather than full Sentry coverage. You can scope the connection to one organization or project, which sets defaults and hides discovery tools. For self-hosted Sentry there is a stdio transport (npx @sentry/mcp-server) that takes a user auth token; its AI-powered search tools need an OpenAI, Azure OpenAI, Anthropic or OpenRouter key.

Best for

• Teams already on Sentry
• Debugging production errors from the editor
• Self-hosted Sentry via the stdio transport

Use it when

Your app reports to Sentry and you want the coding agent to pull issue details, errors and traces while it works on a fix.