Skip to main content
Chief hosts an MCP server at https://mcp.chief.bot/mcp, so Claude Code, Cursor, and other compatible AI tools can work with your Chief Project without you installing or running a local server. Connect once, then ask your AI tool to search or manage chats, assets, labels, actions, Live Sessions, skills, memories, and Projects.

​
Before you connect

You need:
  • A Chief Personal Access Token. The hosted server does not use a browser sign-in or OAuth flow.
  • The ID of the Project you want the AI tool to use. You can copy it from the Project URL; Chief Project IDs begin with project_.
  • An MCP client that supports remote Streamable HTTP servers and custom request headers.
⚠️ Important: Treat your PAT like a password. Add it only to your MCP client’s secure configuration, never to a prompt, chat message, screenshot, or committed file. Revoke the token if it is exposed.

​
Connect Claude Code

Replace the placeholders, then run:
Restart the Claude Code session after adding the server. Ask Claude to list its MCP tools or use /mcp to confirm that chief is connected.

​
Connect Cursor

  1. Open the command palette.
  2. Choose Cursor Settings › MCP › Add new global MCP server.
  3. Add this configuration with your PAT and Project ID:
Restart Cursor or reconnect the server after saving the configuration.

​
Connect another MCP client

Point any client that supports Streamable HTTP at https://mcp.chief.bot/mcp and send these headers with every request: If a client can set only an Authorization header, use Authorization: Bearer <personal-access-token>. X-API-Key takes precedence if you send both.
ℹ️ Good to Know: Most Chief tools require X-Project-Id. Tools that list, create, or update Projects and manage Project membership can work with the PAT alone.

​
Hosted versus self-hosted

Use the hosted server for the shortest setup: there is no binary to download, local process to keep running, or server infrastructure to maintain. Self-hosting remains available when your organization needs to run the MCP process in its own environment. See the chief-mcp repository for optional stdio and self-hosted HTTP instructions. This is Chief acting as an MCP server for an external AI client. Connecting a custom MCP server into a Chief Action is the opposite direction and uses a different setup.

​
FAQ

No. Connect your MCP client directly to https://mcp.chief.bot/mcp. Install the binary only if you deliberately choose the optional self-hosted setup.
Confirm X-Project-Id contains the Project that owns the resource and that your PAT can access it. A missing or incorrect Project ID is the usual cause for project-scoped tools.
Confirm the client supports remote Streamable HTTP servers and custom headers. Recheck the endpoint and credentials, then restart the client session because MCP configurations may not reload automatically.
Yes, but that is a separate workflow for adding an external tool or destination to Chief. See Connecting a custom MCP server.