Connect Claude Code and Codex to TurboProject with MCP

Step-by-step guide to connecting AI agents like Claude Code and Codex to TurboProject through the Model Context Protocol (MCP) with a personal API token.

TurboProject exposes its whole API as Model Context Protocol (MCP) tools. That means AI agents such as Claude Code and Codex can read plans, update tasks, attach evidence, work in change hubs and war rooms, and apply runbooks, all from your terminal.

  • Endpoint: https://<your-instance>/mcp (streamable HTTP, stateless)
  • Authentication: a personal API token, sent as Authorization: Bearer tpat_...
  • Permissions: the agent acts as you. It sees and changes exactly what you can in the web app, and everything it does is recorded in the audit log under your name.

1. Create an API token

  1. Sign in to TurboProject and open My integrations from the avatar menu.
  2. Under API tokens & AI agents, enter a name (for example claude-laptop) and how many days it should be valid, then click Create.
  3. Copy the token. It is shown only once.
  4. Store it as an environment variable, never in a file you commit:
# ~/.bashrc, ~/.zshrc or your password manager's shell integration
export TURBOPROJECT_TOKEN='tpat_...'

Use one token per machine or agent, so you can revoke one without breaking the others.

2. Connect your agent

Claude Code

For yourself, in every project:

claude mcp add --transport http --scope user turboproject https://<your-instance>/mcp \
  --header 'Authorization: Bearer ${TURBOPROJECT_TOKEN}'

Keep the single quotes. Claude Code then stores the literal ${TURBOPROJECT_TOKEN} and reads the variable when it starts, so the token itself is never written to its config.

To share the server with a repository’s team, commit an .mcp.json at the repository root instead. Everyone uses their own token from the environment:

{
  "mcpServers": {
    "turboproject": {
      "type": "http",
      "url": "https://<your-instance>/mcp",
      "headers": { "Authorization": "Bearer ${TURBOPROJECT_TOKEN}" }
    }
  }
}

Check it with claude mcp list, or /mcp inside a session.

Codex

codex mcp add turboproject --url https://<your-instance>/mcp \
  --bearer-token-env-var TURBOPROJECT_TOKEN

Check it with codex mcp list.

3. Try it

Ask your agent, for example:

  • “List my open tasks in TurboProject.”
  • “Show the blocked tasks in project ACME-DC1 and why they are blocked.”
  • “Attach this show ip bgp summary output as evidence to task CUT-04.”
  • “Summarise the war room for the core outage and post a status update.”

Tool names follow <service>_<method>, for example project_list_tasks or room_record_step_outcome. Read-only tools are marked as such, so agents can ask before calling anything that changes data.

Troubleshooting

Symptom Cause
401 / “use an API token” The variable is not set in the shell that started the agent, or the token expired or was revoked.
Calls fail with “permission denied” Your account lacks that permission in that project. The agent has exactly your access.
The agent does not show the server Restart the agent after adding it, then check claude mcp list or codex mcp list.

Ready to put your projects in motion?

See TurboProject on your own change process in a 30-minute walkthrough. No slides, just the product.