Clarabit Docs

Install

One connector URL works everywhere: https://mcp.clarabit.ai/mcp. Each host ends with a Google sign-in. Until Clarabit is listed in the Claude and ChatGPT directories, add it as a custom connector.

Claude

1. Open Claude, go to Settings then Connectors, and choose Add custom connector.
2. Name it Clarabit and paste https://mcp.clarabit.ai/mcp as the server URL.
3. Click Connect, sign in with Google, then ask: "What's waiting on me in Clarabit?"

ChatGPT

1. Open Settings, then Apps and Connectors, and enable Developer mode if needed.
2. Create a connector named Clarabit with MCP server URL https://mcp.clarabit.ai/mcp and OAuth authentication.
3. Sign in with Google, add the Clarabit connector to a chat, and ask: "What's waiting on me?"

Claude Code

Run:

claude mcp add --transport http clarabit https://mcp.clarabit.ai/mcp

Then run /mcp, pick Clarabit, and complete the Google sign-in.

Codex, Cursor, and Other MCP Hosts

Any host that supports remote MCP servers over Streamable HTTP with OAuth can connect with the URL alone. For Codex, add this to ~/.codex/config.toml:

[mcp_servers.clarabit]
url = "https://mcp.clarabit.ai/mcp"

For Cursor, add this to .cursor/mcp.json or ~/.cursor/mcp.json:

{
  "mcpServers": {
    "clarabit": { "url": "https://mcp.clarabit.ai/mcp" }
  }
}

What OAuth Grants

Scope	What it allows
clarabit:read	Read projects, tasks, pages, comments, context entries, labels, and workflow state.
clarabit:write	Create and update tasks, pages, comments, and context; claim and move tasks; record agent sessions.

The token identifies you. The tool acts under your permissions and can only do what you could do in the web app. Clarabit never sees your conversation, only the tool calls the host makes. See the privacy policy for what is logged about each call.

Tools

All hosted MCP tools are prefixed cla_. Start each session with cla_bootstrap; it returns your projects, assignments, active claims, available tasks, and conventions.

Read

cla_bootstrap, cla_list_projects, cla_get_project, cla_list_tasks, cla_get_task, cla_get_workflow, cla_generate_prompt, cla_list_pages, cla_get_page, cla_list_page_versions, cla_get_page_version, cla_list_page_comments, cla_prepare_page_comment_anchor, cla_context_list, cla_context_get, cla_context_package, and cla_list_labels.

Write

cla_create_task, cla_update_task, cla_start_task, cla_submit_task, cla_claim_task, cla_release_task, cla_add_comment, cla_add_label_to_task, cla_remove_label_from_task, cla_log_time, cla_create_page, cla_update_page, cla_archive_page, cla_restore_page, cla_restore_page_version, cla_create_page_comment, cla_update_page_comment, cla_resolve_page_comment, cla_unresolve_page_comment, cla_context_create, cla_context_update, cla_upload_image, cla_upload_task_attachment, and cla_upload_comment_attachment.

Session

cla_session_start, cla_session_progress, cla_session_event, cla_session_blocked, cla_session_heartbeat, cla_heartbeat, cla_session_complete, and cla_session_fail.

How a Handoff Works

Every task in Clarabit carries its own record: the spec, decisions, comments, and a log of each session that touched it. When an agent picks up a task, it calls cla_bootstrap and then reads the task or context package, so it starts from that shared record instead of a blank chat. As it works it claims the task, logs progress and evidence, and moves the status under the workflow rules. The next person or tool asks "what's waiting on me?" and gets the same record.

Support and Changes

Email support@clarabit.ai. A person reads it. Tell us which host you are using and what you asked it to do; a screenshot of the tool call helps. Release notes live in the public changelog.