BusinessMCP

MCP servers for VS Code

VS Code reads MCP servers from a workspace or user mcp.json, so a server can be scoped to one repository or to every project you open.

Last updated September 16, 2026

Connect BusinessMCP to VS Code

One entry for every tool you have connected, rather than one config block per server with its own credential. Add this to .vscode/mcp.json:

{
  "servers": {
    "businessmcp": {
      "type": "http",
      "url": "https://businessmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mcph_YOUR_KEY_HERE"
      }
    }
  }
}
  1. 1Create .vscode/mcp.json in your repository, or use the user-level config to make the server available in every project.
  2. 2Paste the block above with a key from your BusinessMCP dashboard.
  3. 3Reload the window. The server appears in the chat view tool picker.
  4. 4Ask an agent-mode question that needs real data and it calls the tool instead of inferring an answer.
VS Code MCP docs

Frequently asked questions

Workspace config or user config?

Workspace config travels with the repository, so a teammate who clones it gets the same servers — which is what you want for anything project-specific. User config is right for your personal staples. Do not commit a credential either way: reference an environment variable or an input.

Does this work in Copilot agent mode?

Yes. MCP servers configured this way show up as tools in agent mode, alongside the built-in ones.

Can I point it at a local server instead?

Yes — a stdio entry runs a local command rather than calling a URL. A hosted endpoint is simpler when several people need the same tools, since nobody has to install anything.

One endpoint, every tool, in VS Code

Connect your stack once and it is reachable from VS Code — and from every other AI you use — without a config block per server.

Get started free

Free plan available · No credit card