Clarabit MCP changelog
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.