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.
ViaductArchitecture model01 — One model, many ways in.Read / Write / Export / Observe
02Start here
Four ways the model gets in and out
AIMCP serverCursor, Claude Code and any MCP client read the model and write back to it.DeveloperAPI/SDKEverything the editor does, under /api/v1 — with an OpenAPI document to generate a client from.EventsWebhooksSigned events when elements, connections or a change set move.ContractsOpenAPIImport a spec onto a container, or export its contracts back out.
03Everything else
And the rest of what it speaks
AICursorAsk about the architecture, and let it write back.AIClaude CodeThe model in the terminal, change sets included.AIClaude DesktopThe same server, for questions rather than code.AIVS CodeAny editor that speaks MCP. The config is three lines.AIChange setsWork pinned to a version, with criteria the agent must prove.DesignFigmaComponents point at real frames; colours and spacing come in by name.ContractsProtobuf & gRPC.proto sources on the endpoints that speak them.ExportPlantUMLSequence diagrams are PlantUML source. Take it with you.ExportJSONThe whole model, in and out as one file.ExportPNG & SVGRender a diagram or a sequence for a slide or a README.ShareShare linksRead or edit without an account, until you revoke it.
Connect the model to your workflow.
Create a free account