VS Code reads its servers from .vscode/mcp.json. 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.
It lives next to your other editor settings, so it can be committed and shared with the team.
mkdir -p .vscode && touch .vscode/mcp.json
Take it from any server card here — the address comes from our last successful handshake.
MCP tools are available to the agent, not to plain chat completion. If nothing shows up, check which mode you are in before touching the config.
.vscode/mcp.json
Browser Use →
{
"servers": {
"browser-use": {
"type": "http",
"url": "https://api.browser-use.com/v3/mcp"
}
}
}
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.
Written from how VS Code reads its config, not from its release notes.
Editor 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.
Adds servers by command, so nothing to edit by hand. Handles both local processes and remote endpoints, including OAuth logins.
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.
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.