MCP server

The TunnelHQ MCP server lets an AI assistant — Claude, Cursor, Windsurf, or Cline — drive TunnelHQ directly. Ask it to test a config, add a monitor, or check on an incident, and it does the work through the same API you'd use yourself.

On this page

Ask AI about this page

Open in ClaudeOpen in ChatGPTRun with TunnelHQ MCP

What it can do

Once connected, your assistant has ~30 tools. The highlights:

  • Test any VPN config, share link, or subscription URL and report whether it connects — including parallel batch tests.
  • Create, update, and list monitors — plus bulk update and bulk delete with a dry-run so you can preview a sweeping change before it lands.
  • Search monitors across every project in the organization.
  • Run on-demand checks and read back the results.
  • Look at incidents and help you resolve them.
  • Manage subscription URLs and trigger syncs.
  • Check plan usage and quotas before it does something rate-limited.

Claude Code

Add the server

terminal
claude mcp add tunnelhq --scope user \
  --env TUNNELHQ_API_KEY="uk42_..." \
  -- npx -y --ignore-existing https://tunnelhq.com/releases/mcp/latest/tunnelhq-mcp.tgz

Verify it registered

terminal
claude mcp list

Cursor & Windsurf

Add the server to your MCP config — ~/.cursor/mcp.json for Cursor, or ~/.codeium/windsurf/mcp_config.json for Windsurf:

mcp.json
{
  "mcpServers": {
    "tunnelhq": {
      "command": "npx",
      "args": ["-y", "--ignore-existing", "https://tunnelhq.com/releases/mcp/latest/tunnelhq-mcp.tgz"],
      "env": {
        "TUNNELHQ_API_KEY": "thq_..."
      }
    }
  }
}

Always on the latest build

The install commands pass npx --ignore-existing, and the tarball at /releases/mcp/latest is served with no-cache headers — so every session picks up the current MCP server automatically. Pin a specific version with a /releases/mcp/v<x>/… URL if you'd rather.

Bring an API key

The MCP server authenticates with a TunnelHQ API key (Starter plan and up). Generate one under Developers → API Keys.

Copy-ready setup with your key baked in

The in-app Install page renders all of the above with your actual API key filled in, plus tabs for each client — the fastest way to get connected.
PreviousCLINextWebhooks