Save WorkBaton checkpoints and WorkStash notes for AI agent handoffs.
If you already use A2CR, the a2cr mcp server is the piece that lets your assistant work with it directly. Save WorkBaton checkpoints and WorkStash notes for AI agent handoffs.
A2CR is an open-source local MCP workspace for AI agent handoffs. It lets Codex, Claude Code, Cursor, and other MCP-capable agents save WorkBaton checkpoints, store temporary WorkStash notes, coordinate through WorkThreads, and resume long coding work from a fresh AI window.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
explain_a2cr_flows — explain when to use WorkBaton, WorkStash, or WorkThreadsget_account_limits — show current local workspace limits for Slots, retention, and WorkStashshould_save_workbaton — advise whether a compact WorkBaton checkpoint is useful nowsave_context — save a WorkBaton checkpoint in the local workspaceresume_context — find and load the right WorkBaton for a fresh AI windowload_context — load a specific Slot number or named WorkBatonlist_contexts — list active WorkBaton Slotsdelete_context — delete a named WorkBaton Slotshould_use_work_stash — advise whether a supporting note belongs in WorkStashstore_work_stash — store a temporary supporting note in the local workspaceget_work_stash — retrieve a referenced WorkStash entrylist_work_stash — list WorkStash metadata and quota usageConfiguration is passed through the environment: A2CR_LOCAL_DB, A2CR_UI_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. A2CR's toolset — explain_a2cr_flows, get_account_limits, should_save_workbaton and 10 more — is a fair guide to whether it matches your workflow. It is maintained by a2cr; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against A2CR's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| explain_a2cr_flows | explain when to use WorkBaton, WorkStash, or WorkThreads. |
| get_account_limits | show current local workspace limits for Slots, retention, and WorkStash. |
| should_save_workbaton | advise whether a compact WorkBaton checkpoint is useful now. |
| save_context | save a WorkBaton checkpoint in the local workspace. |
| resume_context | find and load the right WorkBaton for a fresh AI window. |
| load_context | load a specific Slot number or named WorkBaton. |
| list_contexts | list active WorkBaton Slots. |
| delete_context | delete a named WorkBaton Slot. |
| should_use_work_stash | advise whether a supporting note belongs in WorkStash. |
| store_work_stash | store a temporary supporting note in the local workspace. |
| get_work_stash | retrieve a referenced WorkStash entry. |
| list_work_stash | list WorkStash metadata and quota usage. |
| delete_work_stash | delete a WorkStash entry that is no longer needed. |
Generic MCP JSON:
```json
{
"mcpServers": {
"a2cr": {
"command": "a2cr-mcp",
"args": [],
"env": {
"A2CR_LOCAL_DB": "/optional/path/to/a2cr.db"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| A2CR_LOCAL_DB | Configuration value read at startup. | Optional |
| A2CR_UI_URL | Endpoint or connection string the server talks to. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.