Connect YADL with MCP

YADL's Model Context Protocol (MCP) connection gives a compatible AI host a controlled way to compose, validate, inspect, save, storyboard, and export diagrams for the account that authorizes it. MCP does not grant browser automation, direct database access, administrator access, or access to another user's YADL work.

Authorize a connection

In a production connection, the MCP host directs you through YADL authorization. The host receives only the permissions you approve, while YADL maps that authorization to short-lived, owner-scoped server-side delegation for each request.

Follow the connection flow presented by your approved MCP host or YADL integration. Review the requested scopes before approving it. If the host cannot complete YADL authorization, do not paste an API key into a chat, tool argument, or public configuration; contact the integration owner or Support.

Available workflow

The MCP connection exposes capability discovery and authorized resource search, deterministic diagram composition, validation and inspection, bounded repair, private storyboard checkpoints, owner-scoped document retrieval and optimistic saving, export-quota discovery, idempotent export submission, export status, and completed-artifact packaging.

For compatible hosts, YADL can also open a compact live preview and a user-requested fullscreen workspace. The workspace supports local source edits, undo/redo, fit, validation, and explicit saving. It is not a replacement for all editor features: catalog dependencies, direct-canvas authoring, timeline authoring, and embedded export controls are outside this embedded workflow.

Safe use with AI agents

Ask the agent to inspect capabilities before composing an asset, validate before saving, and check export quota before submitting video. A generated diagram remains editable YADL source; review it before you save or distribute it. Storyboard images and export retrieval paths are private to the authorized account, so do not publish or share those paths as public links.

If an optimistic save conflicts with a newer document version, preserve the local draft and use the host's reload-latest or save-as-copy recovery option. A repair stops after three attempts and returns remaining diagnostic issues rather than silently claiming a failed visual is correct.

Connection boundaries

Connector credentials stay in server-side host configuration and are never accepted as model-visible tool inputs or returned in a YADL view. YADL's current agent profile is intentionally bounded to explanatory diagrams and does not advertise unsupported chart, media, narration, social-publishing, or unrestricted asset workflows.

For direct server integration, review Agent API. For the language used in returned workspaces, see YADL source language.