Skip to content

VS Code Busymate DevTools test_pac_connection

How to: VS Code Busymate DevTools test_pac_connection

client:VS Code transport:streamable-http tool:test_pac_connection

Add Busymate DevTools to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "busymate-devtools": {
      "type": "http",
      "url": "https://mcp.busymate.dev"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something test_pac_connection does. VS Code lists the server's tools on connect and calls test_pac_connection itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Busymate DevTools's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.