Your AI agent, working your Basecamp fields.

Sign in. Add the server, then type /mcp inside Claude Code and choose Authenticate. A browser tab opens on Assistant: pick the workspace, click Allow, and you are connected.

claude mcp add --transport http assistant https://api.getassistant.io/mcp

With a token instead. Paste this into Claude Code. It runs the command and proves the server works with a first tool call.

Add the Assistant for Basecamp MCP server to this environment, then verify it.

Server name: assistant
Transport: Streamable HTTP
URL: https://api.getassistant.io/mcp
Auth header: Authorization: Bearer afb_YOUR_TOKEN

Do this:
Run: claude mcp add --transport http assistant https://api.getassistant.io/mcp --header "Authorization: Bearer afb_YOUR_TOKEN"
If my MCP config already lists other servers, add this one beside them and leave the rest untouched. If a server named "assistant" already exists, tell me before changing it.

Then tell me if the server only loads after a restart. Once it is loaded, call assistant_list_fields and show me the fields in my workspace.

Rules: do not print the token back to me and do not store it anywhere except the MCP config. Use Basecamp's own API or CLI for projects, to-dos, cards and people. Assistant's tools cover custom fields, statuses, tags, saved views, automations and WIP limits only.

By hand, one command in your terminal:

claude mcp add --transport http assistant https://api.getassistant.io/mcp --header "Authorization: Bearer afb_YOUR_TOKEN"

The command adds one server next to any you already have. If a server named assistant already exists, give this one another name, for example assistant-basecamp.

claude.ai and Claude Desktop. Settings → Connectors → Add custom connector. Name it Assistant, paste the URL below, then Connect. Assistant opens: pick the workspace, click Allow. Every Claude surface that shares your account sees the connector.

https://api.getassistant.io/mcp

ChatGPT. Settings → Connectors → Create, with the same URL. Some plans keep custom connectors behind Developer mode under Advanced settings; turn it on first.

With a token instead, Claude Desktop only. Open claude_desktop_config.json (Settings → Developer → Edit Config), add the entry below inside the "mcpServers" object, save, and restart the app. It runs the mcp-remote bridge, which carries your token to the endpoint.

The file already lists servers? Paste this entry after the last one inside "mcpServers", with a comma between entries, and keep the rest of the file as it is.

"assistant": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://api.getassistant.io/mcp",
    "--transport",
    "http-only",
    "--header",
    "Authorization:${AUTH_HEADER}"
  ],
  "env": {
    "AUTH_HEADER": "Bearer afb_YOUR_TOKEN"
  }
}

Starting from an empty file? Use the whole thing:

{
  "mcpServers": {
    "assistant": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.getassistant.io/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer afb_YOUR_TOKEN"
      }
    }
  }
}

Watch it done first. The steps below, recorded in the Codex app.

Sign in from the Codex app.

1. Open Settings and click Plugins in the sidebar.
2. Click Add at the top right.
3. Choose Add MCP server.
4. Set Type to Streamable HTTP.
5. Name: Assistant.
6. URL: https://api.getassistant.io/mcp.
7. Leave the bearer token and headers empty.
8. Click Save.
9. In the MCPs tab, search for Assistant.
10. Click Authenticate next to it. Sign in with Basecamp, pick the workspace, click Allow.

Or from the terminal. The first command adds the server, the second opens the same sign-in:

codex mcp add assistant --url https://api.getassistant.io/mcp
codex mcp login assistant

The CLI, the desktop app, and the IDE extension share ~/.codex/config.toml, so either route covers all three.

With a token instead. Paste this into Codex.

Add the Assistant for Basecamp MCP server to this environment, then verify it.

Server name: assistant
Transport: Streamable HTTP
URL: https://api.getassistant.io/mcp
Auth header: Authorization: Bearer afb_YOUR_TOKEN

Do this:
1. Add this to ~/.codex/config.toml:
   [mcp_servers.assistant]
   url = "https://api.getassistant.io/mcp"
   bearer_token_env_var = "ASSISTANT_TOKEN"
2. Put the token in the ASSISTANT_TOKEN environment variable in my shell profile.
If my MCP config already lists other servers, add this one beside them and leave the rest untouched. If a server named "assistant" already exists, tell me before changing it.

Then tell me if the server only loads after a restart. Once it is loaded, call assistant_list_fields and show me the fields in my workspace.

Rules: do not print the token back to me and do not store it anywhere except the MCP config. Use Basecamp's own API or CLI for projects, to-dos, cards and people. Assistant's tools cover custom fields, statuses, tags, saved views, automations and WIP limits only.

By hand, add to ~/.codex/config.toml with the token in the ASSISTANT_TOKEN environment variable:

[mcp_servers.assistant]
url = "https://api.getassistant.io/mcp"
bearer_token_env_var = "ASSISTANT_TOKEN"

Each server is its own [mcp_servers.<name>] table, so paste this block below any servers already in the file. Nothing else in the file changes.

Codex cloud tasks do not read this file. From a cloud task, use the plain HTTPS routes.

Sign in. Cursor, Windsurf, and any client that supports OAuth for remote servers: add a Streamable HTTP server with the URL and no header. The sign-in opens the first time the client connects.

"assistant": {
  "type": "http",
  "url": "https://api.getassistant.io/mcp"
}

With a token instead. Cline, Gemini CLI, and any agent that can edit its own MCP config. Paste this into the chat:

Add the Assistant for Basecamp MCP server to this environment, then verify it.

Server name: assistant
Transport: Streamable HTTP
URL: https://api.getassistant.io/mcp
Auth header: Authorization: Bearer afb_YOUR_TOKEN

Do this:
Add a Streamable HTTP server named "assistant" with that URL and header to your own MCP configuration, in the format your config uses.
If my MCP config already lists other servers, add this one beside them and leave the rest untouched. If a server named "assistant" already exists, tell me before changing it.

Then tell me if the server only loads after a restart. Once it is loaded, call assistant_list_fields and show me the fields in my workspace.

Rules: do not print the token back to me and do not store it anywhere except the MCP config. Use Basecamp's own API or CLI for projects, to-dos, cards and people. Assistant's tools cover custom fields, statuses, tags, saved views, automations and WIP limits only.

By hand, the entry Cursor, Windsurf and Cline read. If the config already lists servers, paste it after the last one inside "mcpServers", with a comma between entries:

"assistant": {
  "type": "http",
  "url": "https://api.getassistant.io/mcp",
  "headers": {
    "Authorization": "Bearer afb_YOUR_TOKEN"
  }
}

Starting from an empty file? Use the whole thing:

{
  "mcpServers": {
    "assistant": {
      "type": "http",
      "url": "https://api.getassistant.io/mcp",
      "headers": {
        "Authorization": "Bearer afb_YOUR_TOKEN"
      }
    }
  }
}

Any script or automation tool, and Codex cloud tasks. Sign-in is for MCP clients; a script uses a token, which opens the same routes the extension uses. The workspace id is in the dashboard's URL.

curl -H "Authorization: Bearer afb_YOUR_TOKEN" https://api.getassistant.io/accounts/WORKSPACE_ID/custom-fields

Every route answers JSON. The Postman collection in the backend repo documents each one; the tool table below names the families.