Hub Proxy Client Configuration

This page covers client-specific configuration for connecting to PodWarden through Hub. See Hub MCP Proxy for the overview and tunnel setup.

Endpoint: https://mcp.podwarden.com/mcp

Auth: Your Hub API key (pwc_...) as a Bearer token.

Claude Desktop

Claude Desktop uses mcp-remote as a stdio-to-HTTP bridge. Requires Node.js.

{
  "mcpServers": {
    "podwarden": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.podwarden.com/mcp",
        "--header",
        "Authorization:${PODWARDEN_HUB_TOKEN}"
      ],
      "env": {
        "PODWARDEN_HUB_TOKEN": "Bearer pwc_YOUR_API_KEY_HERE"
      }
    }
  }
}

The token is placed in env rather than inline in args to avoid a Windows escaping bug.

Claude Code

claude mcp add --transport http podwarden https://mcp.podwarden.com/mcp \
  --header "Authorization: Bearer pwc_YOUR_API_KEY_HERE"

Cursor

Open Cursor Settings > MCP > "Add new global MCP server" and paste:

{
  "mcpServers": {
    "podwarden": {
      "url": "https://mcp.podwarden.com/mcp",
      "headers": {
        "Authorization": "Bearer pwc_YOUR_API_KEY_HERE"
      }
    }
  }
}

Other clients

Any MCP-compatible client can connect using the Streamable HTTP transport.

Troubleshooting

Instance shows "Disconnected" in Hub

• Verify Hub URL and API key are correct (Settings > Hub > Test Connection)
• Check that the tunnel toggle is enabled (Settings > MCP > Hub MCP Tunnel)
• Check PodWarden container logs for "Hub tunnel" messages
• If the instance was recently restarted, wait for the reconnect (up to 5 minutes with backoff)

Tool calls return errors

• Check the access level — if set to "Read Only", mutating tools will return errors
• Verify the tool exists on your instance (list_instance_tools)
• Check PodWarden's MCP Activity Log for error details

"No instances connected" from AI client

• Your PodWarden instance may not have connected yet. Check Hub Dashboard > MCP.
• The tunnel takes a few seconds to establish after PodWarden starts.
• If recently restarted, wait for reconnect (up to 5 minutes with backoff).