MCP fact tools catch up to the REST API
MCP agents can now comment on tasks, turn on a stack, tag on create, and title notes and memos, with facts addressed by block id. For builders on MCP.
Until now, what an agent could do over MCP lagged behind the REST API. A handful of everyday actions a model needed were missing from MCP, so an agent that could read your workspace still had to hand work back to a REST caller to finish it. Facts were also referenced by slug, which could change under an integration's feet.
What's new over MCP
- Comment on tasks directly from an agent.
- Turn on a stack so new facts can land in it.
- Add tags inline when you create a record, instead of a second call.
- Title notes and memos on create.
- Clear task fields, not just set them.
- Richer responses on create, so an agent gets back what it just made without a follow-up read.
One fix
list_notesno longer includes task comments. Those are already listed with tasks, so the same comment stopped appearing in two places.
Why it matters
An agent working your tasks board can now leave a comment, open a stack to receive facts, and tag a contact as it creates it, all in one pass over MCP, instead of stopping short at the edge of what the protocol exposed. Block ids are stable, so an integration that writes one down keeps pointing at the same block even after a slug is edited.
Where to find it
The new tools are live over MCP. See the API docs at api.getnoan.com.
Good to know, and this is a breaking change: MCP fact tools now take block ids only and no longer accept slugs. If your current MCP integration references facts by slug, update it to use block ids. List your stacks and blocks to map your existing slugs to their ids before you switch.