MCP clients - Chief Help

Connect to Chief’s hosted Streamable HTTP server at https://mcp.chief.bot/mcp. You do not need to install chief-mcp or run a local process. Replace <api-key> with a Chief PAT and <project-id> with the Project you want the client to use. The help center covers token creation in API access & personal access tokens.

Hosted server

Claude Code
Cursor

claude mcp add chief --transport http https://mcp.chief.bot/mcp \
  --header "X-API-Key: <api-key>" \
  --header "X-Project-Id: <project-id>"

Open the command palette → Cursor Settings → MCP → Add new global MCP server, then add:

{
  "mcpServers": {
    "chief": {
      "url": "https://mcp.chief.bot/mcp",
      "headers": {
        "X-API-Key": "<api-key>",
        "X-Project-Id": "<project-id>"
      }
    }
  }
}

Any Streamable HTTP client can use the same endpoint and headers. If a client only accepts an Authorization header, use Authorization: Bearer <api-key>.

Optional self-hosted setup

Install the chief-mcp binary only when you want to run the server yourself — see MCP server → Optional self-hosted install. The quickest way to configure a self-hosted client is the chief CLI (install it too), which fills in the installed binary path and your credentials:

chief mcp config claude   # Claude Code / Claude Desktop
chief mcp config cursor   # Cursor
chief mcp config codex    # Codex

It prints where each client expects the snippet:

Claude Code — .mcp.json (project) or ~/.claude.json (user), or run claude mcp add chief -- chief-mcp stdio
Cursor — .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
Codex — ~/.codex/config.toml (emitted as TOML)

No chief CLI? Every snippet below also works pasted in by hand — you only need the chief-mcp binary. To configure a client by hand, use the snippets below. Replace <api-key> and <project-id> with your values — the help center covers where the token comes from in API access & personal access tokens.

Stdio transport

Use stdio when the agent runs the server locally as a subprocess.

Claude Code
Claude Desktop
Cursor
Codex
VS Code

claude mcp add chief \
  -e CHIEF_API_KEY=<api-key> \
  -e CHIEF_PROJECT_ID=<project-id> \
  -- chief-mcp stdio

Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "chief": {
      "command": "chief-mcp",
      "args": ["stdio"],
      "env": {
        "CHIEF_API_KEY": "<api-key>",
        "CHIEF_PROJECT_ID": "<project-id>"
      }
    }
  }
}

Open the command palette → Cursor Settings → MCP → Add new global MCP server, then add:

{
  "mcpServers": {
    "chief": {
      "command": "chief-mcp",
      "args": ["stdio"],
      "env": {
        "CHIEF_API_KEY": "<api-key>",
        "CHIEF_PROJECT_ID": "<project-id>"
      }
    }
  }
}

Add to ~/.codex/config.toml:

[mcp_servers.chief]
command = "chief-mcp"
args = ["stdio"]
env = { CHIEF_API_KEY = "<api-key>", CHIEF_PROJECT_ID = "<project-id>" }

Create .vscode/mcp.json in your workspace (or add it to your user settings):

{
  "servers": {
    "chief": {
      "type": "stdio",
      "command": "chief-mcp",
      "args": ["stdio"],
      "env": {
        "CHIEF_API_KEY": "<api-key>",
        "CHIEF_PROJECT_ID": "<project-id>"
      }
    }
  }
}

Windsurf and other clients that read an mcpServers block use the same snippet as Cursor.

Self-hosted HTTP transport

Use HTTP for remote or web-based integrations. Start the server, then point the client at its endpoint with credentials in the request headers.

chief-mcp http --addr :8080 --path /mcp

The server listens on http://localhost:8080 and exposes the MCP endpoint at /mcp using Streamable HTTP.

Claude Code
Cursor

claude mcp add chief --transport http http://localhost:8080/mcp \
  --header "Authorization: Bearer <api-key>" \
  --header "X-Project-Id: <project-id>"

{
  "mcpServers": {
    "chief": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer <api-key>",
        "X-Project-Id": "<project-id>"
      }
    }
  }
}

Verify the connection

After configuring a client, restart its session — MCP servers are long-lived stdio processes that don’t hot-reload.

Claude Code's /mcp panel showing the chief server connected with 44 tools — In Claude Code, /mcp shows the Chief server connected with all 44 tools.

Then ask the agent to list its tools, or test the server directly with the MCP Inspector (requires Node.js):

npx @modelcontextprotocol/inspector chief-mcp stdio

Click Connect, then List tools to confirm the server responds.

FAQ

I changed the config but the client still does not see the server.

Restart the client session. MCP servers are long-lived stdio processes and do not hot-reload after a config change.

Should I use the hosted server, stdio, or self-hosted HTTP?

Use the hosted server for the shortest setup. Choose stdio only when a local agent must launch your own binary, or self-hosted HTTP when your organization must operate the server in its own network.

Is there a faster way than writing the config by hand?

Yes. chief mcp config claude, chief mcp config cursor, or chief mcp config codex print a ready-to-paste snippet with the binary path and credentials filled in.

How do I test the server without an agent?

Run the MCP Inspector against it: npx @modelcontextprotocol/inspector chief-mcp stdio, then click Connect and List tools.

​Hosted server

​Optional self-hosted setup

​Stdio transport

​Self-hosted HTTP transport

​Verify the connection

​FAQ

Hosted server

Optional self-hosted setup

Stdio transport

Self-hosted HTTP transport

Verify the connection

FAQ