Developers

Developer docs cover the public integration surfaces around Mini Agency: MCP, embeddable forms, the public renderer, static exports, document concepts, and mutation behavior.

Main surfaces

• MCP server: connect external MCP clients over HTTP JSON-RPC.
• Active-site rule: target the correct workspace and site when a token can access more than one surface.
• MCP reference: generated from the committed tool catalog. Start with Core tools.
• Embeddable forms script: submit forms from external pages safely.
• Public renderer: understand staging and published routes.
• Static exports: consume exported artifacts.
• Document model: pages, artboards, nodes, styles, components, collections, and snapshots.
• Mutations: persistent writes, local optimistic edits, SSE fan-out, and undo history.

Integration rule

Mini Agency is multi-tenant. Every integration that reads or writes a site must prove both identity and target site. Never assume the default site is the one the user meant. For MCP, use the active-site rule. For HTTP APIs, pass the site headers or route parameters required by the endpoint.

Related docs

• Guides for product workflows.
• Agencies for white-label operations.