Bring your own agent, over MCP

You have probably already picked an agent you like. We did not want M2 to ask you to switch. Instead, M2 speaks the Model Context Protocol (MCP), so the tools you run today can plug straight into the canvas.

What “connected” means

Once an agent is connected over MCP, it can do the things a teammate can:

• Read the current canvas — nodes, components, and design-system references.
• Add and modify UI on the shared surface, live.
• Stay in sync with everyone else editing at the same time.

No copy-paste, no exporting screenshots into a chat window. The agent sees what you see.

One protocol, many agents

Because MCP is an open standard, M2 does not have to bless one agent over another. Claude Code, Cursor, Codex — or whatever you reach for next — all connect through the same door. Your canvas stays the constant; the agents are interchangeable.

Connecting takes a minute. See Connect over MCP for the steps.