Developers
Developers
Build on Desyn — the architecture, the document model and its operations, the Agent REST API, the MCP server, the TypeScript SDK and how to contribute.
Desyn is built around one idea: a single, precise document model that every client, the server, the AI and external agents edit in exactly the same way — through transactions of small operations. If you understand the model, you understand the whole system.
ArchitectureHow the Rust engine, Convex, the clients and the AI fit together.Document modelDesigns, nodes, paint, styles and invariants — the frozen contract.Operations & transactionsThe eight operations, undo, and how invalid ops are handled.Sync protocolHow edits flow through Convex and reach every client.Agent API (v1)REST endpoints for designs, assets, the agent and workflows.MCP serverLet Claude and other agents design with Desyn's tools.TypeScript SDKTyped client, document builders and transaction helpers.ContributingRepository layout, development setup and the CLA.
Choosing an integration#
| You want to | Use |
|---|---|
| Let an AI assistant (Claude, an IDE agent) create and edit designs | The MCP server |
| Automate Desyn from a script, backend or CI | The Agent API or the TypeScript SDK |
| Make precise programmatic edits | Transactions through the API |
| Read a design's structure for your own analysis | Describe |
| Change Desyn itself | The source, under the license |
The Agent API and MCP server are part of Pro and the self-hosted edition.