Introduction to Ardot MCP

Ardot MCP Server is a Model Context Protocol (MCP) server implementation from Tencent Design Ardot. It lets AI agents (such as WorkBuddy, CodeBuddy Code, Cursor, Claude Code, and Codex) read and operate on Ardot design files directly, enabling two-way design–code workflows.

You can think of the MCP Server as an authenticated API for large language models: agents access an application's data and capabilities through a standard protocol. In Ardot, agents can read the current design file context and create or modify designs on the canvas.

What you can do

With Ardot MCP enabled, you can:

• Read and write the design canvas: Use an AI agent to create and edit frames, component instances, text, layout, and styles—turning design intent into Ardot files directly.
• Convert designs to code: Select a page or frame and have the agent pull layer structure, styles, screenshots, and design guidelines to generate frontend code that better matches the design.
• Extract design context: Bring variables (design tokens), component libraries, layout trees, and more into your IDE—useful for design systems and component-driven development.
• Manage design systems: Read and write multi-theme variables, search and build style guides, reuse local component libraries, and keep brand and specs consistent.
• Export and deliver assets: Scan exportable resources and export nodes as PNG, JPEG, SVG, and other formats to fit design handoff workflows.

These capabilities fold work that used to require switching between design tools and the IDE into a single agent conversation—for example generating code from designs, iterating UI on the canvas, syncing tokens, or reviewing layout.