Connect any MCP server to your client.
Config-file-accurate install steps for every major MCP client.
Chrome DevTools MCP server in Claude Code.
Give Claude Code a real browser to debug against. One CLI command registers the official Chrome DevTools MCP server, and your agent can inspect, profile, and screenshot live pages without leaving the terminal.
Chrome DevTools MCP server in Claude Desktop.
Let Claude Desktop open a real Chrome window, read console errors, and profile page performance. One JSON entry in claude_desktop_config.json and a full restart is all it takes.
Chrome DevTools MCP server in Cline.
Cline writes your frontend code inside VS Code — Chrome DevTools MCP lets it check the result in a real browser. Here's the cline_mcp_settings.json entry and where that file actually hides.
Chrome DevTools MCP server in Continue.dev.
Continue.dev configures MCP servers in YAML, not JSON. Here's the exact block for Chrome DevTools MCP — globally in config.yaml or per-project in .continue/mcpServers/ — and the indentation traps to avoid.
Chrome DevTools MCP server in Cursor.
Cursor's agent can already write your frontend — with Chrome DevTools MCP it can also load the page, read the console, and profile what it built. Setup is one mcp.json entry and a toggle.
Chrome DevTools MCP server in LangChain.
No config file here — LangChain connects to MCP servers in code. Use langchain-mcp-adapters to spawn Chrome DevTools MCP over stdio and hand its browser tools to any agent you build.
Chrome DevTools MCP server in n8n.
n8n's MCP Client Tool node speaks HTTP, while Chrome DevTools MCP speaks stdio. The fix is a small gateway process — here's the bridge command and the node settings to point at it.
Chrome DevTools MCP server in VS Code (GitHub Copilot).
Copilot's agent mode supports MCP natively in VS Code — but the config key is "servers", not "mcpServers", and that one detail breaks most copy-pasted setups. Here's the correct config.
Chrome DevTools MCP server in Windsurf.
Give Cascade a live Chrome to verify its frontend work in. Windsurf keeps all MCP config in one global file — ~/.codeium/windsurf/mcp_config.json — and here's exactly what goes in it.
Chrome DevTools MCP server in Zed.
Zed calls them context servers, and they live in your main settings.json under a context_servers key. Here's the entry that gets Chrome DevTools MCP running in Zed's Agent Panel.
Context7 MCP server in Claude Code.
Stop Claude Code from hallucinating APIs that changed two majors ago. Context7 pulls current, version-specific library docs into the session — and registering it takes one command.
Context7 MCP server in Claude Desktop.
Ask Claude Desktop about a library and get answers grounded in this week's docs, not last year's training data. One entry in claude_desktop_config.json connects Context7's 57.1k-star doc server.
Context7 MCP server in Cline.
Cline writes whole features autonomously — which makes stale API knowledge expensive. Wire up Context7 through cline_mcp_settings.json and every run can check current library docs first.
Context7 MCP server in Continue.dev current docs, not training data.
Wire Upstash's Context7 into Continue.dev with one YAML block, so the docs your model reads match the library versions in your package.json.
Context7 MCP server in Cursor version-accurate docs in Composer.
One mcp.json entry gives Cursor's agent live access to up-to-date library documentation from Context7 — no more code written against last year's API surface.
Context7 MCP server in LangChain docs lookups as agent tools.
Load Context7's documentation tools into a LangChain agent with langchain-mcp-adapters — about ten lines of Python, no config file involved.
Context7 MCP server in n8n live docs inside your workflows.
Point n8n's MCP Client Tool node at Context7's hosted endpoint and your AI Agent workflows can pull current library documentation mid-run.
Context7 MCP server in VS Code (GitHub Copilot) ground Copilot in real docs.
Give Copilot's agent mode access to version-specific library documentation with a .vscode/mcp.json entry — note the key is "servers", not "mcpServers".
Context7 MCP server in Windsurf fresh docs for Cascade.
Add Context7 to Windsurf's mcp_config.json and Cascade can fetch current, version-specific library documentation before it writes a line of code.
Context7 MCP server in Zed context_servers, configured right.
Zed calls MCP servers "context servers" and configures them in settings.json — here's the exact entry for Context7 and the restart step that makes it stick.
Exa MCP server in Claude Code real web search in the terminal.
Exa is a remote MCP server, so connecting Claude Code is one CLI command — no local process, no npm install, just a URL with your API key.
Exa MCP server in Claude Desktop AI-grade search for Claude.
Claude Desktop's config file launches local processes, and Exa lives in the cloud — mcp-remote bridges the two in one mcpServers entry.
Exa MCP server in Cline web search for an autonomous coder.
Connect Exa's hosted search endpoint to the Cline VS Code extension through cline_mcp_settings.json — reachable in two clicks from the Cline panel.
Exa MCP server in Continue.dev search the live web from YAML.
Bridge Exa's hosted search endpoint into Continue.dev's config.yaml so chat and agent sessions can search, crawl, and pull real code examples.
Exa MCP server in Cursor the agent that can Google properly.
Cursor speaks to remote MCP servers natively, so connecting Exa's hosted search endpoint is a three-line mcp.json entry — no local proxy needed.
Exa MCP server in LangChain web search your agents can call.
Connect Exa's hosted MCP endpoint to a LangChain agent over streamable HTTP with langchain-mcp-adapters — no subprocess, no Node dependency.
Exa MCP server in n8n web search for your workflows.
Exa gives n8n's AI Agent node fast, intelligent web search, crawling, and code-context lookup over MCP. There's no config file to edit — you wire it up with a single MCP Client Tool node.
Exa MCP server in VS Code (GitHub Copilot) live web results in agent mode.
Wire Exa's hosted MCP endpoint into VS Code's mcp.json and Copilot's agent mode gets web search, crawling, and code-context lookup — no local process required.
Exa MCP server in Windsurf give Cascade the live web.
One serverUrl entry in mcp_config.json and Windsurf's Cascade agent can search the web, crawl pages, and pull current code context through Exa.
Exa MCP server in Zed web search in the Agent Panel.
Add Exa as a context server in Zed's settings.json and the Agent Panel gains web search, crawling, and code-context retrieval — configured the Zed way, under context_servers.
Figma Context MCP server in Zed designs in, code out.
Figma-Context-MCP feeds your Figma files to Zed's agent so it can implement a design in one shot. Here's the exact settings.json entry, where to get the token, and what to check when the server doesn't show up.
Figma-Context-MCP server in Claude Code designs to code in one shot.
One claude mcp add command connects Claude Code to your Figma files, so it can read layout, components, and styles directly instead of guessing from screenshots.
Figma-Context-MCP server in Claude Desktop let Claude read your design files.
Edit claude_desktop_config.json once and Claude Desktop can pull frames, components, and styles straight from Figma — useful for spec reviews, design QA, and handoff prep, not just code generation.
Figma-Context-MCP server in Cline design-aware autonomous coding.
Configure cline_mcp_settings.json from the Cline panel and the VS Code extension can fetch Figma frames mid-task — reading real layout data while it builds your UI.
Figma-Context-MCP server in Continue.dev Figma data in your open-source assistant.
A short YAML block in config.yaml — or a drop-in file under .continue/mcpServers/ — connects Continue's agent mode to your Figma files via the figma-developer-mcp package.
Figma-Context-MCP server in Cursor the design-to-code pairing.
Cursor plus Figma-Context-MCP is the combination this server was practically built for: paste a frame link into Composer and get framework-accurate markup from real layout data.
Figma-Context-MCP server in LangChain design data for programmatic agents.
No config file here — LangChain connects to MCP servers in code via langchain-mcp-adapters. A few lines of Python give your agent Figma file access as ordinary tools.
Figma-Context-MCP server in n8n design data in automated workflows.
n8n's MCP Client Tool node speaks HTTP, and Figma-Context-MCP can serve HTTP — run the server once, point the node at it, and your workflows can read Figma files.
Figma-Context-MCP server in VS Code (GitHub Copilot) Copilot that has seen the mock.
An entry in .vscode/mcp.json puts your Figma files within reach of Copilot's agent mode — with VS Code's inputs mechanism keeping the API token out of the committed file.
Figma-Context-MCP server in Windsurf Cascade reads the design first.
Add the figma-developer-mcp package to mcp_config.json and Windsurf's Cascade agent can fetch real frame data from Figma before it writes a line of UI code.
Filesystem MCP server in Claude Code scoped file access, one command.
mcp-server-filesystem gives Claude Code controlled read/write/search access to directories outside your project — added with a single claude mcp add command or a project .mcp.json.
Filesystem MCP server in Claude Desktop give Claude your folders.
Claude Desktop can't touch your files by default. mcp-server-filesystem changes that — read, write, and search on exactly the directories you allow, configured in claude_desktop_config.json.
Filesystem MCP server in Cline files beyond the workspace.
Cline edits your open project natively — mcp-server-filesystem extends its reach to other directories you choose, through one stdio entry in cline_mcp_settings.json.
Filesystem MCP server in Continue.dev stdio server, YAML config.
Run mcp-server-filesystem as a local stdio process under Continue.dev — a five-line YAML block that gives your Continue agent fenced read/write/search access to chosen directories.
Filesystem MCP server in Cursor a fence around file access.
Give Cursor's agent fenced access to directories outside the open project — mcp-server-filesystem runs locally via npx and is configured in one mcp.json entry.
Filesystem MCP server in LangChain local files, loaded as agent tools.
Give a LangChain agent read, write, and search access to local files through the mcp-server-filesystem MCP server. There's no config file to edit — you wire it up in a few lines of Python with langchain-mcp-adapters.
Filesystem MCP server in n8n file access for workflow agents.
n8n's MCP Client Tool node connects over SSE or streamable HTTP — and mcp-server-filesystem speaks stdio. Here's how to bridge the two and give your n8n AI Agent read, write, and search access to local files.
Filesystem MCP server in VS Code (GitHub Copilot) agent mode, beyond the workspace.
Copilot's agent mode can already edit files in your open workspace. Adding mcp-server-filesystem extends that reach to any directory you choose — with explicit, configurable scope in .vscode/mcp.json.
Filesystem MCP server in Windsurf give Cascade the whole disk — or one folder.
Wire mcp-server-filesystem into Windsurf's Cascade agent through mcp_config.json. One JSON entry, one refresh, and Cascade can read, write, and search directories beyond the project it has open.
Filesystem MCP server in Zed context servers, configured in settings.json.
Zed calls MCP servers context servers and configures them in its main settings.json. Here's the exact entry for mcp-server-filesystem, plus how to confirm Zed's agent can actually see the tools.
Firecrawl MCP server in Claude Code the web, from your terminal.
One CLI command or one .mcp.json entry gives Claude Code scrape, crawl, search, and extract tools backed by Firecrawl. Here's both routes, plus how to debug when the server doesn't register.
Firecrawl MCP server in Claude Desktop give Claude real web access.
Claude Desktop can't browse the web on its own plan limits alone — Firecrawl gives it proper scrape, crawl, and extract tools. The config is one JSON block; the gotchas are the file path and the restart.
Firecrawl MCP server in Cline scraping tools for your VS Code agent.
Cline manages MCP servers from its own panel inside VS Code, with per-tool auto-approval on top. Here's the cline_mcp_settings.json entry for Firecrawl and the panel-specific things to check when it fails.
Firecrawl MCP server in Continue.dev web data in your open-source assistant.
Continue configures MCP servers in YAML — either globally in config.yaml or as per-project files under .continue/mcpServers/. Here's the exact block for Firecrawl and the YAML-specific failure modes.
Firecrawl MCP server in Cursor let your editor read the web.
Cursor's agent gets scrape, search, crawl, and extract tools from one mcp.json entry. The config takes a minute; the toggle and the green dot are where people get stuck.
Firecrawl MCP server in LangChain scraping tools, loaded as code.
LangChain has no config file for MCP — you wire servers up in code with langchain-mcp-adapters. Here's the exact Python to load Firecrawl's tools into an agent, and the async gotchas that follow.
Firecrawl MCP server in n8n scraping inside your workflows.
n8n's MCP Client Tool node speaks SSE and Streamable HTTP, not stdio — so connecting Firecrawl means running it in SSE mode first. Here's the command, the node settings, and the Docker networking trap.
Firecrawl MCP server in VS Code (GitHub Copilot) agent mode meets the live web.
Copilot's agent mode reads MCP servers from .vscode/mcp.json — with a built-in secrets mechanism most clients lack. Here's the Firecrawl config that keeps your API key out of the file.
Firecrawl MCP server in Windsurf give Cascade the open web.
Windsurf's Cascade agent picks up MCP servers from mcp_config.json under ~/.codeium/windsurf. One Firecrawl entry, one refresh, and your agent can scrape, search, and crawl.
Firecrawl MCP server in Zed web scraping at editor speed.
Zed's Agent Panel takes MCP servers through a context_servers block in settings.json. Here's the exact entry for Firecrawl and the restart-and-PATH checklist when it doesn't connect.
GitHub MCP server in Claude Code repos, issues, and PRs by prompt.
GitHub's official MCP server is remote — no npx, no local process. One claude mcp add command, an OAuth handshake via /mcp, and Claude Code can manage repos, issues, pull requests, and Actions.
GitHub MCP server in Claude Desktop your repos in the chat window.
GitHub's official MCP server is remote, and Claude Desktop's config file only speaks stdio — so the reliable path is the mcp-remote bridge in claude_desktop_config.json. Here's the exact entry, plus the Connectors alternative.
GitHub MCP server in Cline wired into VS Code.
Cline can already write code autonomously inside VS Code. Add the official GitHub MCP Server and it can also open PRs, triage issues, and read workflow runs — all through one remote endpoint, no local install.
GitHub MCP server in Continue.dev one YAML block away.
Continue.dev reads MCP servers from config.yaml. Point it at GitHub's hosted MCP endpoint and your Continue agent can manage issues, PRs, and workflows without leaving the editor.
GitHub MCP server in Cursor from mcp.json to merged PR.
Cursor's agent gets full GitHub reach — issues, pull requests, Actions — through one entry in mcp.json pointed at GitHub's hosted MCP endpoint.
GitHub MCP server in LangChain tools for your agent, in code.
LangChain has no config file for MCP — you wire servers up in code with langchain-mcp-adapters. Here's how to load GitHub's hosted MCP server into a LangChain agent in a dozen lines of Python.
GitHub MCP server in n8n a node, not a config file.
n8n connects to MCP servers through the MCP Client Tool node. Point it at GitHub's hosted endpoint and any AI Agent node in your workflow can manage repos, issues, and PRs.
GitHub MCP server in VS Code (Copilot) first-party on both ends.
VS Code's Copilot agent and the GitHub MCP Server are built by the same company, and it shows: OAuth sign-in instead of token pasting, and a one-line mcp.json entry.
GitHub MCP server in Windsurf Cascade meets your repos.
Windsurf's Cascade agent picks up GitHub's hosted MCP server through one entry in mcp_config.json — issues, PRs, and Actions become part of the agentic flow.
GitHub MCP server in Zed context_servers, configured.
Zed calls MCP servers context servers and configures them in settings.json. Here's how to run GitHub's official MCP server for Zed's Agent Panel using the Docker distribution.
MCP Toolbox for Databases in Windsurf.
Give Cascade a real connection to your database. One entry in mcp_config.json and Windsurf's agent can inspect schemas and run queries through Google's MCP Toolbox.
MCP Toolbox for Databases in Zed.
Wire Google's database MCP server into Zed's Agent Panel with a context_servers entry, so the editor can introspect schemas and run queries against your actual database.
MCP Toolbox for Databases in Claude Code your database, one claude mcp add away.
Google's MCP Toolbox for Databases connects an agent to Postgres, MySQL, BigQuery, and more through a declarative tools file. Here's how to register it with Claude Code — CLI or .mcp.json — and debug it when it won't connect.
MCP Toolbox for Databases in Claude Desktop ask your database questions in plain English.
Connect Google's MCP Toolbox for Databases to Claude Desktop and chat with your data through tools you define — not raw SQL. Exact claude_desktop_config.json entry for Mac and Windows, plus the restart and log dance.
MCP Toolbox for Databases in Cline schema-aware coding, query-checked answers.
Hook Google's MCP Toolbox for Databases into Cline so the VS Code agent can run your sanctioned queries while it codes. The config lives in cline_mcp_settings.json, reached through Cline's own MCP panel.
MCP Toolbox for Databases in Continue.dev declared in YAML, end to end.
Continue.dev configures MCP servers in YAML — and Google's MCP Toolbox for Databases defines its tools in YAML too. Two files, one pipeline: config.yaml launches the server, tools.yaml decides what your agent can query.
MCP Toolbox for Databases in Cursor real schema, real queries, while you code.
Stop pasting schemas into Cursor's chat. Google's MCP Toolbox for Databases gives the agent named, parameterized query tools over your actual database — configured in one mcp.json entry and a toggle.
MCP Toolbox for Databases in LangChain governed SQL tools for your Python agents.
Connect Google's MCP Toolbox for Databases to a LangChain agent through langchain-mcp-adapters. Because the Toolbox serves MCP over HTTP natively, the cleanest wiring is a running container plus a URL — no subprocess management in your agent code.
MCP Toolbox for Databases in n8n no bridge needed — it speaks HTTP natively.
Most stdio MCP servers need a gateway before n8n can use them. Google's MCP Toolbox for Databases doesn't: it serves MCP over HTTP out of the box, so the MCP Client Tool node connects straight to it.
MCP Toolbox for Databases in VS Code (GitHub Copilot) Copilot agent mode meets your real schema.
Add Google's MCP Toolbox for Databases to VS Code so Copilot's agent mode can run the queries you've sanctioned — defined once in tools.yaml, registered once in .vscode/mcp.json, shared with the whole team.