Hud Remote MCP Server

📘

Most users should use the local MCP via the Hud IDE extension or npm. Remote MCP exists for cases where that isn't possible — typically because you can't install the Hud IDE extension, or because your workflow runs in an environment that doesn't support local MCP servers.

What is Hud Remote MCP?

A hosted MCP server at https://mcp.hud.io/mcp.

There are two distinct ways to authenticate, each meant for a different use case:

• OAuth — for humans using an MCP client interactively (Cursor, Claude Code, Jetbrains) on your laptop.
• API key (X-Hud-Mcp-Key) — for machines, CI, and agentic workflows. Get your key at app.hud.io/settings/api-keys (or ask Hud support if you don't have one).

Cursor

Add Hud to your Cursor mcp.json (project-level at <project>/.cursor/mcp.json or user-level at ~/.cursor/mcp.json).

OAuth (interactive use):

{
  "mcpServers": {
    "hud": {
      "type": "http",
      "url": "https://mcp.hud.io/mcp",
      "auth": {
        "CLIENT_ID": "XyvD6NaPGbrpOL9mxglq7KUYuPXbyNB4"
      }
    }
  }
}

Toggle hud on in Cursor Settings → Tools & MCP; Cursor opens a browser tab to sign you in.

The CLIENT_ID is identical for all users and should not be changed.

API key (automations, Cursor Background Agents, headless setups):

{
  "mcpServers": {
    "hud": {
      "type": "http",
      "url": "https://mcp.hud.io/mcp",
      "headers": {
        "X-Hud-Mcp-Key": "<Your MCP key>"
      }
    }
  }
}

Claude Code

OAuth (interactive use):

Run this on your terminal:

claude mcp add -t http hud \
  --client-id XyvD6NaPGbrpOL9mxglq7KUYuPXbyNB4 \
  --callback-port 2425 \
  https://mcp.hud.io/mcp

Then go into Claude Code and authenticate by running /mcp and following the OAuth flow.

The CLIENT_ID is identical for all users and should not be changed.

API key (CI, scripted agents, containers):

claude mcp add -t http hud https://mcp.hud.io/mcp \
  -H "X-Hud-Mcp-Key: <Your MCP key>"