MCPwell

Home › Clients › VS Code

VS Code

The two JSON shapes below are copied from the VS Code MCP docs. The Figma and Chrome DevTools blocks use the URL or package on those registry entries. The registry package for Playwright on this site is not the package name in the VS Code docs example.

From the VS Code docs

The VS Code MCP docs describe two file shapes. A workspace .mcp.json, and the user Copilot config, use a top-level mcpServers object. A .vscode/mcp.json file uses a top-level servers object. The examples below are copied from that page. They name GitHub's Copilot MCP endpoint and @microsoft/mcp-server-playwright. Those strings come from the VS Code docs, not from a re-check of the GitHub or Playwright registry entries on this site. Our Playwright fact sheet uses the package name on the registry entry, which is different.

{
  "mcpServers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp"
    },
    "playwright": {
      "command": "npx",
      "args": ["-y", "@microsoft/mcp-server-playwright"]
    }
  }
}
{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp"
    },
    "playwright": {
      "command": "npx",
      "args": ["-y", "@microsoft/mcp-server-playwright"]
    }
  }
}

Figma, remote

VS Code
{
  "servers": {
    "figma": {
      "type": "http",
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

Chrome DevTools, local

VS Code
{
  "servers": {
    "chrome-devtools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}

Every fact sheet