Integrations
Connect Viaduct to what you already run
The model is only worth keeping if the rest of your tooling can read it. Everything below works today — an agent that edits the architecture, an API with a client generator behind it, events when something changes, and files you can take with you.
Start here
Four ways the model gets in and out
MCP server
Cursor, Claude Code and any MCP client read the model and write back to it.
API/SDK
Everything the editor does, under /api/v1 — with an OpenAPI document to generate a client from.
Webhooks
Signed events when elements, connections or a change set move.
OpenAPI
Import a spec onto a container, or export its contracts back out.
Everything else
And the rest of what it speaks
Cursor
Ask about the architecture, and let it write back.
Claude Code
The model in the terminal, change sets included.
Claude Desktop
The same server, for questions rather than code.
VS Code
Any editor that speaks MCP. The config is three lines.
Change sets
Work pinned to a version, with criteria the agent must prove.
Protobuf & gRPC
.proto sources on the endpoints that speak them.
PlantUML
Sequence diagrams are PlantUML source. Take it with you.
JSON
The whole model, in and out as one file.
PNG & SVG
Render a diagram or a sequence for a slide or a README.
Share links
Read or edit without an account, until you revoke it.