A website agent can finish the page while you are away from the editor. Decide who can publish that work before connecting it to a client site.
What the remote connection adds
Framer announced Framer MCP on October 22. The connection lets compatible AI clients work on the canvas, manage CMS content, and publish a site. Framer says the editor can stay closed while the agent works.
Its connection guide describes support for remote Model Context Protocol servers and OAuth authorization. MCP is the interface through which the client calls Framer tools. OAuth lets you approve the account connection. The client still supplies the model and its own usage plan or credits.
That makes the connection useful for a specific builder task: revising an existing Framer project from an agent you already use. It also puts account access and release review into the same conversation.
Check the account before the prompt
According to Framer, the agent can access the canvas, components, supported settings, and CMS in projects available to the connected account. It follows that account’s permissions. Approving the connection deserves the same care as giving a collaborator access to the project.
Before authorizing it, identify the account and intended project. Then ask the agent to describe the change it plans to make. A request to replace one paragraph should have a smaller scope than a request to rebuild a landing page.
Review the branch before publishing
Framer says edits remain in the project until you or your agent publishes them. Its guide recommends using branches to review changes. The agent can affect the live site when explicitly asked to publish, so write that instruction deliberately.
I would start with one page and one CMS entry on a branch. Ask for a revised page introduction and a matching CMS summary. This is a proposed evaluation workflow; we have not run a hands-on Framer MCP test.
- Record the original page text and CMS field value.
- Ask the agent to make the named edits without publishing.
- Inspect the branch in Framer, including the mobile layout and linked content.
- Publish only after review, then check the public URL and the CMS-driven page.
Checking both destinations catches a practical problem: a page can look finished while its connected summary still contains the old message. Our Canva Craft design review uses a related principle: inspect the editable result and the words it contains.
Keep the older connection where its features are needed
Framer calls MCP the recommended connection for agents. Its documentation also says the older @framer/agent CLI supports additional workflows, including localization. Both remain supported while the remote connection gains feature parity.
Check a current workflow against that list before migrating it. If a localization job depends on the CLI, a successful MCP page edit does not establish that the whole job can move. For automation that spans several services, our Zapier task-usage guide explains why the unit of work also needs checking.
Read the connection details
Which part of your Framer workflow would you delegate first: a page revision or a CMS update?
