Clarabit MCP changelog
2.15.4 — October 28, 2026
Released for both the hosted connector at https://mcp.clarabit.ai/mcp and the npm package @limeadelabs/clarabit-mcp. The changes below are relative to 2.8.0. If you installed an earlier 2.9–2.15 version from npm, its new tools and views start working with this release, because the Clarabit endpoints they call are now live. Update to 2.15.4 anyway.
What changed in each connection type
| Capability | Local MCP (npm / stdio) | Cloud MCP (hosted) |
|---|---|---|
| Google Chat, Docs and Calendar meetings (read, as you) | New | New |
| Granola meeting notes and transcripts (read, as you) | New | New |
| Attio records and list entries (read, as the workspace) | New | New |
| Intercom (Fin) conversations (read, as the workspace) | New | New |
| Interactive views in ChatGPT and Claude (MCP Apps) | New | New |
cla_open_clarabit home view |
New | New |
Structured brief pages (format and spec) |
New | New |
| Links on factory run results; GitLab MR / GitHub PR recognition | New | New |
Read your work tools
These tools only read. Clarabit returns what the source says and doesn’t store it. Every result includes a source_notice marking it as source material, not instructions. Each tool needs a connection, set up once on Clarabit’s Connections page. If a connection is missing or needs redoing, the error says so in plain words and includes the link.
- Google, connected per person:
cla_google_list_chat_spaces,cla_google_search_chat,cla_google_read_chat,cla_google_read_doc,cla_google_list_meetings. Chat messages that share a file, card or link read as what they share. Meetings come with the notes Docs attached to each. - Granola, per person, with their own API key:
cla_granola_list_folders,cla_granola_list_notes,cla_granola_read_note. The transcript is returned only when asked for. - Attio, connected once per workspace by an owner:
cla_attio_search_records,cla_attio_get_record,cla_attio_list_entries. - Intercom (Fin), connected once per workspace by an owner:
cla_fin_search_conversations,cla_fin_read_conversation.
Restricted members (access to only some projects) get a permission error from the Attio and Intercom tools. Long text is capped per call; when that happens, the result says it was truncated.
Interactive views (MCP Apps)
Tools that answer with a task, a page, a factory run or the Needs-you list now include a view: _meta.ui.resourceUri (MCP Apps) and openai/outputTemplate (ChatGPT). The server serves the views as resources (ui://clarabit/task, ui://clarabit/page, ui://clarabit/run, ui://clarabit/needs-you, ui://clarabit/home, mime text/html;profile=mcp-app) on both transports.
- Buttons call Clarabit tools through your AI app: Claim (open tasks only), Accept, Reject with a reason, and a comment box on task cards that calls
cla_add_comment. - Opening or closing an item inside a view tells the model which item is on screen, so “comment on this task” means the one you’re looking at.
- Views load no external scripts, styles, fonts or frames, and never fetch on their own.
- AI apps without MCP Apps support ignore the view and use the text result as before.
New tool: cla_open_clarabit (read-only, no arguments) returns the bootstrap payload and opens the home view: what needs you, your projects and your tasks. In ChatGPT it also adds Clarabit to the sidebar. In apps that can’t draw views, the answer gives the Clarabit web address to open instead.
Structured brief pages
cla_create_page, cla_update_page and cla_factory_run_finish accept format: "spec" with a spec object. A spec holds blocks for stats, callouts, tables (rows that name a task show it live), lists, sources, text and checks. Clarabit renders it as a brief and keeps a plain-text version for sharing and email. Validation errors come back word for word, so your AI app can fix the spec and retry. Pages without format work as before.
Links and errors
cla_factory_run_finishtakes an optionallinksarray (up to 10, http or https, optionaltitle). Clarabit keeps them on the run and adds them to the task the run’staskinput names.cla_add_task_linkrecognizes GitLab merge requests and GitHub pull requests.- When a response from Clarabit is replaced on the way (for example a
502 Bad Gatewayfrom a proxy), the error now says so, with the request ID and codeclarabit_unreadable_response, instead of only the status text.
Cloud MCP
The hosted catalog goes from 57 tools to 71. If the new tools or views don’t appear, reconnect the Clarabit connector in your AI app.
Local MCP
The local catalog has 74 tools: the 71 cloud tools plus the three local file upload tools. To update:
npm install -g @limeadelabs/clarabit-mcp@2.15.4
If your AI app launches a pinned version, update the pin to 2.15.4. Then restart the MCP process, or reconnect, so it loads the new version.
Related platform changes
The matching Clarabit app release adds the Connections page and cloud factory runs that can read the assignee’s connections (only the assignee can turn that on). These are server-side changes that apply to both connection types. See the product release notes.
Usage and error measurements
Unchanged since 2.7.0. Tool arguments and results are excluded. To turn telemetry off for a local installation, set CLARABIT_TELEMETRY=off. See the privacy policy.
2.8.0 — October 20, 2026
Released for both the hosted connector at https://mcp.clarabit.ai/mcp and the npm package @limeadelabs/clarabit-mcp. The changes below are relative to 2.7.0.
What changed in each connection type
| Capability | Local MCP (npm / stdio) | Cloud MCP (hosted) |
|---|---|---|
| Factories: list, read, propose, and run with step reporting | New | New |
Factories
Eight tools let your AI app find and run your team’s factories (saved, versioned workflows) and report each step back to Clarabit:
cla_list_factories,cla_get_factory: find a factory and read its recipe (inputs, steps, checks and destination).cla_propose_factory: draft a new factory, or a change to one, for its owner to review.cla_factory_run_start,cla_factory_run_step,cla_factory_run_finish: start a run, report each step, and finish with the result and a pass/fail for each check.cla_factory_run_accept,cla_factory_run_reject: the factory owner accepts the result, or rejects it with a reason.
A factory can hand its accepted result to another factory.
Cloud MCP
The hosted catalog goes from 49 tools to 57.
Local MCP
The local catalog has 60 tools. To update:
npm install -g @limeadelabs/clarabit-mcp@2.8.0
Usage and error measurements
Unchanged since 2.7.0. Tool arguments and results are excluded. To turn telemetry off for a local installation, set CLARABIT_TELEMETRY=off. See the privacy policy.
2.7.0 — September 20, 2026
Released for both the hosted connector at https://mcp.clarabit.ai/mcp and the npm package @limeadelabs/clarabit-mcp. The changes below are relative to 2.6.3.
What changed in each connection type
| Capability | Local MCP (npm / stdio) | Cloud MCP (hosted) |
|---|---|---|
| Attention: list work needing input and inspect the reason | New | New |
| Project initialization and effective instruction retrieval | Added | Added |
| Attach task links and return canonical web URLs | Added | Added |
| Session checkpoints and resume | New | New |
| Session start, heartbeat, progress, events, blockers, completion and failure | Existing tools extended | Newly available |
| Clearer tool titles, descriptions and startup guidance | Updated | Updated |
| Tool usage and error telemetry | Added | Added |
Available in both
- Attention:
cla_list_attentionandcla_get_attention_itemexpose review requests, blockers and other interventions with supporting context. - Project initialization:
cla_bootstrapacceptsproject_id, reports project selection requirements, and directs the app to retrieve the effective project instructions. This supports project templates and shared instructions. - Task links:
cla_add_task_linkattaches a link to a task. Task responses include canonical web URLs, and task context exposes linked merge requests. - Checkpoints and resume:
cla_session_checkpointsaves a structured progress checkpoint;cla_session_resumerecords resumed work. These tools record state; they do not launch a background worker. - Tool guidance: human-readable titles, more specific descriptions and startup instructions help AI apps choose the appropriate Clarabit tools. This guidance does not guarantee that an app will use Clarabit automatically in every conversation.
Cloud MCP
Session lifecycle tools are now available over the hosted connection. Cloud clients can start a session, report progress and blockers, record checkpoints, resume, and report completion or failure.
Keep the session_id returned by cla_session_start and pass it to subsequent session calls. Hosted connections do not keep a local session-ID cache.
The hosted catalog contains 49 tools. Local filesystem upload tools are not exposed through the cloud connector.
Local MCP
Local users already had session lifecycle reporting. Version 2.7.0 extends it with checkpoints, resume and richer reporting contracts, alongside the shared changes above.
The local catalog contains 52 tools, including the three local filesystem upload tools.
To update an existing global installation:
npm install -g @limeadelabs/clarabit-mcp@2.7.0
For a project dependency:
npm install @limeadelabs/clarabit-mcp@2.7.0
If your AI app launches a pinned package version, update that pin to 2.7.0. Restart the local MCP process or reconnect through your app so it loads the new version. Publishing to npm does not update an already-running local process.
Usage and error measurements
This release adds MCP tool usage and error telemetry to help diagnose connection and tool failures. Tool arguments and tool results are excluded from these events.
Local installations can disable telemetry by setting CLARABIT_TELEMETRY=off in the environment used to launch the MCP server. See the privacy policy for data-handling details.
Related platform fixes
The accompanying Clarabit application release fixes page-version history and summaries, improves session liveness and claim renewal, and exposes task merge-request links. These are server-side changes benefiting both connection types.