For AI agents
Caplo's hosted MCP server lets Cursor, Claude, and your own agents read the repository and propose changes inside a draft. People review and publish. Version history and the audit trail show what changed.
One workspace · Changes stay reviewable
Agents read the model your architects keep, write into a draft, and leave a record of what they changed.
Core benefit
Agents do not need a custom export. They can search the repository, follow relations, look at the neighborhood of an entity, and open BPMN. Before they write, they can read the property shapes for this workspace, so new fields match how the team already models.
Example view
Grounded in the repository
Ask what depends on an application. The answer comes from the model.
What depends on the back-office suite?
Claims handling
Process
Policy admin
Application
Billing
Application
Relations, neighborhoods, and BPMN. Same repository the architects maintain.
An agent asks what depends on an application and gets the neighborhood from the repository.
Core benefit
Repository writes go into a draft. The agent creates one or reuses an open draft, updates entities, relations, and BPMN there, and returns a link for review. Publish and delete stay in Caplo. The live model changes only when a person decides it should.
Example view
Review before live
The proposal stays in a draft, and the record starts there.
Draft · Retire back-office suite
History
What changed, and who changed it
Snapshot
The workspace as it was on a given date
Audit
Create, update, delete, and restore. Tagged to the draft.
Publish stays in Caplo. Restore is there if you need the previous version.
A draft holds the proposal. History, snapshots, and the audit trail record it the same way as an edit in Caplo.
Core benefit
These are workflows you can run with your own agent. Caplo gives it the repository, a draft to write in, and a link for review. Someone still has to publish.
Example view
Work you can hand to an agent
The same setup, used on different queues.
Demand intake
Map a request onto capabilities and applications
Repository upkeep
Propose missing relations and stale descriptions
Target-state scenario
A named draft, including a BPMN update
Each one ends as a draft a person can review and publish.
One draft for a demand, a cleanup, or a target-state scenario, ready for someone to review.
Connect
One connection, one workspace. The agent works against that repository and hands changes back as a draft.
https://app.caplo.ai/mcp