Framer’s Updates page dates the launch October 22, 2026 (about October 22–23 Beijing time, depending on the US posting hour). Framer MCP is a remote MCP server that connects compatible AI clients to Framer projects. The product page headline names Claude, Codex, and Cursor; the same page and FAQ also list ChatGPT, Claude Code, Grok, OpenCode, VS Code, Kiro, Notion, Windsurf, Warp, and others that support remote MCP plus OAuth. Once a connection is approved, an agent can work with the canvas, components, supported project settings, and CMS under the Framer account’s permissions. There is no local Framer bridge to install, and the editor does not need to stay open. We have not run the setup or measured edit quality.
The control point that matters for production sites is publish, not connect. Framer’s FAQ states that an agent can change the live site only if asked explicitly to publish. By default, changes stay in the project or on a branch and do not affect the live site until someone publishes. Teams can ask the agent to work on a branch, review against main in Framer, then publish when ready. Connecting MCP is not the same as shipping a live update.
Framer also positions MCP as the recommended replacement for the older External Agents path (the @framer/agent CLI). That local CLI setup still works for some workflows, including localization, while Framer MCP catches up on feature parity. Usage and credits follow whichever AI client is connected, not a separate Framer agent meter described on this page.
For nearby agent-tooling context on DigIntoAI, see Anthropic’s Agent Skills donation to the Agentic AI Foundation, how Claude Code and Cursor compare on price and limits, and Cursor Remote Control for driving local agents from a phone.