Tock MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add tock-mcp -- npx -y tock-mcp

{
  "mcpServers": {
    "tock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tock-mcp"
      ]
    }
  }
}

[mcp_servers.tock-mcp]
command = "npx"
args = ["-y", "tock-mcp"]

{
  "mcpServers": {
    "tock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tock-mcp"
      ]
    }
  }
}

{
  "servers": {
    "tock-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tock-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TOCK_WS_PORT (Concentrator port for the fetchproxy browser bridge (defaults to the fleet-shared 37149). On one machine every MCP shares the concentrator, so move it for ALL of them or not at all), FETCHPROXY_WS_HOST (Bind interface, a literal IP only (anything else is ignored); default 127.0.0.1. Keep on loopback — it exists for ONE topology: a hosted child in its own network namespace), FETCHPROXY_IDENTITY_DIR (Where to store the long-term identity keypair, an absolute path only (anything else is ignored); default ~/.fetchproxy/identity/. Exists for a host that runs a separate child per caller).