Skip to content

VS Code Autonomous 0-DRC PCB Routing Foundry & Hardware MCP Server calligraphy_route_pcb

How to: VS Code Autonomous 0-DRC PCB Routing Foundry & Hardware MCP Server calligraphy_route_pcb

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

Add Autonomous 0-DRC PCB Routing Foundry & Hardware MCP Server to VS Code

  1. 01

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

{
  "servers": {
    "vibe-hardware-mcp": {
      "type": "http",
      "url": "https://calligraphyeda.com/api/v1/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Autonomous 0-DRC PCB Routing Foundry & Hardware MCP Server'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 11 November 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.