VS Code MCP configuration
TL;DR
VS Code stores MCP server configuration in JSON at user or workspace scope. A workspace-scoped config can be committed to the repository so teammates share the same servers.
User vs workspace
User-scoped configuration applies across your editor; workspace-scoped configuration applies to one project. Use workspace scope for project-specific servers, user scope for personal ones.
Configuration example
Each server entry declares how to launch or reach it — a command for a local server or an HTTP endpoint for a remote one. Which fields are accepted depends on the VS Code MCP integration and version.
In this collection
- Best MCP servers →
- How to choose an MCP server →
- Verified MCP servers →
- MCP server comparison methodology →
- MCP registries, directories, and marketplaces →
- MCP servers for databases →
- Read-only database access with MCP →
- MCP servers for developers →
- MCP browser automation →
- MCP servers for search and research →
- MCP servers for productivity →
- MCP servers for DevOps and cloud →
- Enterprise MCP →
- Postgres MCP server guide →
- Playwright MCP →
- MCP server not showing in Claude Desktop →
- Cursor MCP tools not showing →
- MCP connection refused and timeout errors →
- Claude Desktop MCP configuration →
- Remote MCP servers with OAuth →
- MCP server for GitHub →