Connecting Your Coding Tool

Humfrid exposes its tools over the Model Context Protocol (MCP). Any MCP client connects to the same server at https://mcp.humfrid.com/mcp/v3. This page gives the exact config for each supported client.

You need an API key first. The easiest way to get one is the guided flow: sign in at app.humfrid.com, go to Connections → Add an agent, and pick your tool. The setup page generates a key for you (bound to a new agent identity), shows the exact connect command with the key already filled in, and has a built-in Verify the connection check — for most tools you never need to assemble the configs below by hand.

Keys start with mmt_. Workspace admins can also generate keys manually under Settings → API Keys. Replace mmt_your_key_here in every config below with your real key. See Authentication for scopes and rotation.

Transport

Every client connects over HTTP to https://mcp.humfrid.com/mcp/v3. Auth is a static mmt_ key in headers. Preferred when the client allows it: 

{
  "mcpServers": {
    "humfrid": {
      "type": "http",
      "url": "https://mcp.humfrid.com/mcp/v3",
      "headers": {
        "Authorization": "Bearer mmt_your_key_here",
        "X-Api-Key": "mmt_your_key_here"
      }
    }
  }
}

Some clients only accept one header shape (examples below use what each tool expects). Grok Build needs Bearer (dual-send both). Dual-send is safe everywhere the client allows custom headers.

Per-Client Setup

Claude Code

Add the server from the CLI with the HTTP transport:

claude mcp add --transport http humfrid https://mcp.humfrid.com/mcp/v3 \
  --header "Authorization: Bearer mmt_your_key_here"

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

{
  "mcpServers": {
    "humfrid": {
      "url": "https://mcp.humfrid.com/mcp/v3",
      "headers": {
        "X-Api-Key": "mmt_your_key_here"
      }
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your project:

{
  "servers": {
    "humfrid": {
      "type": "http",
      "url": "https://mcp.humfrid.com/mcp/v3",
      "headers": {
        "X-Api-Key": "mmt_your_key_here"
      }
    }
  }
}

Claude Desktop

Claude Desktop connects the same way as the Claude.com web app: add Humfrid as a custom connector and authorize over OAuth. Open Settings → Connectors → Add custom connector, paste https://mcp.humfrid.com/mcp/v3, and approve the authorization prompt. No API key or local proxy is needed — the connector is linked to your Humfrid account and syncs across Claude Desktop and Claude.com.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "humfrid": {
      "serverUrl": "https://mcp.humfrid.com/mcp/v3",
      "headers": {
        "X-Api-Key": "mmt_your_key_here"
      }
    }
  }
}

Grok Build (xAI)

Prefer the guided flow at app.humfrid.com → Connections → Add an agent → Grok Build. Static Humfrid keys need Authorization: Bearer (and should also send X-Api-Key). Do not start browser OAuth for mmt_ keys. 

export HUMFRID_API_KEY=mmt_your_key_here

grok mcp add --transport http humfrid https://mcp.humfrid.com/mcp/v3 \
  --header "Authorization: Bearer mmt_your_key_here" \
  --header "X-Api-Key: mmt_your_key_here"

grok mcp doctor humfrid

Or in ~/.grok/config.toml / project .grok/config.toml:

[mcp_servers.humfrid]
url = "https://mcp.humfrid.com/mcp/v3"
enabled = true

[mcp_servers.humfrid.headers]
Authorization = "Bearer ${HUMFRID_API_KEY}"
X-Api-Key = "${HUMFRID_API_KEY}"

Antigravity

Prefer the guided flow at app.humfrid.com → Connections → Add an agent → Antigravity (config is pre-filled). Shape matches Windsurf (serverUrl + headers): 

{
  "mcpServers": {
    "humfrid": {
      "serverUrl": "https://mcp.humfrid.com/mcp/v3",
      "headers": {
        "X-Api-Key": "mmt_your_key_here"
      }
    }
  }
}
Planning to use code intelligence? Prefer the Authorization: Bearer header form in .mcp.json — the indexer auto-discovers your key from that form. If your client config uses only X-Api-Key (Cursor, VS Code, Windsurf, Antigravity above), export HUMFRID_API_KEY in your shell so the indexer can find the key.
Note: X-Agent-Id is optional. Your agent identity is bound to your API key when you generate it. If a client sends X-Agent-Id, it is treated as an informational tool-type tag (claude-code, cursor, grok-build), not the identity. See Field Reference.

Claude.com Web App

The Claude.com web app connects to Humfrid as a custom connector over OAuth. There is no API key to paste — the connector authorizes against your logged-in Humfrid session.

  1. In Claude.com, open the connector settings and choose Add custom connector.
  2. Paste the MCP URL https://mcp.humfrid.com/mcp/v3.
  3. Authorize when prompted. Claude.com runs the OAuth flow and the connector is linked to your Humfrid account.
The web connector uses OAuth, so it does not need an mmt_ key. The API-key configs above are for coding tools and other local MCP clients.

Verify

After connecting, call the whoami tool. You get back your identity, assigned tasks, and team context, which confirms the connection works.