
Framer MCP is Framer's official server that lets AI agents like Claude, ChatGPT, Cursor and Codex read and edit your Framer project. Connect it once with OAuth, paste your project link, and ask for changes in plain language. It is strongest on content work: CMS items, copy, featured and ordered content, and new pages built from your existing layouts. Have the agent work on a branch, review the branch in Framer, then merge and publish yourself.
Most Framer MCP guides stop at installation. This one covers what happens after: the workflow we roll out to client marketing teams as a Framer Enterprise Partner, prompts that work, a checklist to run before you merge, and the failures we have already seen on real projects.
See it on real builds: Framer sites we have shipped for funded teams →
What is Framer MCP?
MCP (Model Context Protocol) is an open standard that lets AI agents connect to apps and use them. Framer launched its official MCP server on October 22, 2026. It runs remotely at https://mcp.framer.com/mcp, so there is no local bridge to install and the Framer editor doesn't need to be open.
Once you approve the connection, the agent works with your account's permissions. It can:
create and update pages and layouts across desktop, tablet and phone breakpoints, reusing your project's styles and components
create CMS collections and items, and update structured content
inspect metadata, headings, alt text and page structure for SEO and content issues
create branches so changes can be reviewed before they are merged or published
combine Framer with everything else in your AI client: files, Google Docs, Ahrefs, HubSpot, research
What it can't do yet: localization isn't supported at launch. For that, use Framer's older local CLI (@framer/agent), which is still supported while the MCP catches up.
Framer MCP vs External Agents: which one to use
Framer now has two official ways to connect an agent:
Framer MCP | External Agents | |
|---|---|---|
How it connects | Remote server, OAuth sign-in | Local bridge, set up with |
Works with | Claude, ChatGPT, Codex, Cursor, Grok and any remote MCP client | Agents running on your computer: Claude Code, Codex, Cursor, Gemini CLI, Windsurf |
Framer open? | No | Runs alongside your local setup |
Use it for | Almost everything: pages, CMS, SEO review, branches | Localization, or if your team already runs it |
Our advice: marketing teams should use Framer MCP. Keep External Agents for developers who need localization.
One warning: many "Framer MCP" guides published before October 2026 describe community plugins. Those ask you to keep a plugin open in Framer or edit Claude Desktop's config file. If a guide tells you to do either, it predates the official server. You don't need those steps any more.
Framer MCP vs Framer's built-in AI
Framer MCP (external agent) | Framer's built-in agent | |
|---|---|---|
Where you work | Claude, ChatGPT, Cursor, Codex, Windsurf and others | Inside the Framer editor |
Editor open? | No | Yes |
Billing | Your AI tool's plan | Framer AI credits |
Context | Your docs, files and other connected tools | The project only |
Best for | Repeatable content and CMS work, bulk edits, audits | Quick visual tweaks while designing |
The real advantage is context. In Claude, the article you drafted an hour ago, the brief in your Google Doc and the Framer project are all in one conversation. "Insert the article we just wrote" becomes a one-line request.
How to set up Framer MCP
Every client signs in with OAuth. A workspace admin may need to approve MCP connections first. Ask them before you start, so you aren't left stuck halfway through.
Claude (web or desktop app)
Click +, then Plugins, then Browse plugins. Search for Framer and click Connect.
Sign in to Framer and click Allow.
Claude Code
Then authorize in the browser window that opens.
ChatGPT or Codex
Install Framer from ChatGPT's plugin directory, or in Codex run:
Wait for "Authentication complete".
Cursor
Add Framer from the Cursor Marketplace, or open Customize → MCPs and add a remote HTTP server named framer with the URL https://mcp.framer.com/mcp.
Then, in any client:
Paste the full project link from Framer's address bar. The project name alone isn't enough. The agent can reach every project your Framer account can open, so if you manage client sites or have old test projects, always name the project and check which one it edited.
Set tool permissions. Set read tools to "always allow". For client teams we also set editing tools to "always allow", as long as the agent works on a branch (next section). Keep publishing as a human step.
Test with a read-only question:
For edits, use your strongest model at medium effort. For read-only questions, a faster model is fine.
The workflow that keeps your live site safe
Framer MCP can publish if you explicitly ask it to. That convenience is also the risk. Every client team we train uses this loop:
Ask on a branch. Start every editing prompt with "Work on a new branch."
Read the agent's summary. It lists what it changed and what it couldn't do. The second list is your to-do list.
Open the branch in Framer and switch between it and main to compare.
Run the pre-merge checklist (below).
Merge or delete. If the branch looks right, merge to main, publish to staging, check it, then publish to production. If it doesn't, ask for a fix on the same branch, or delete the branch and nothing has changed.
The branch is what makes this safe to hand to a marketing team. Even a bad request ends with a branch you delete.
How to write a prompt that works first time
The prompts that fail are almost always vague. The ones that work have five parts:
Part | Example |
|---|---|
Project |
|
Safety | "Work on a new branch." |
Location | "On the customer stories page, in the main grid section only" |
Exact item | "the article titled 'Q3 product update'" (copied from the live site) |
Constraint | "Keep it as a draft. Don't change any other page." |
Follow-up requests in the same chat go onto the same branch, so batch related changes and review them once.
If your site was built by someone who has since moved on, an agent can only run it well when the project is tidy: clean CMS collections, real components rather than detached copies, and a predictable page structure. This is the kind of Framer build we do →
Six jobs Framer MCP handles well
These are the jobs client teams run every week, each with a prompt you can copy.
1. Add a blog article, with FAQs and schema
Drag in a Markdown or Word file, or point to an article Claude wrote earlier in the same chat.
The agent creates the CMS item with the title, slug, body and FAQs, and often adds structured data too. You still set the author, upload the cover and social images, and pick related posts.
2. Swap featured posts, podcasts or editor's picks
Clicking through CMS toggles to do this is tedious and easy to get wrong. With the agent, it's a single request.
3. Reorder a grid
"Main grid section only" matters here. Without it, one client's agent also tried to reorder the hero, which was a custom code component, and it failed.
4. Build a page from an existing layout
Create any form first and give the agent its ID. Otherwise it may reuse another page's form instead of asking you for one.
5. Replace copy and legal text
AI is good at copy work. For legal pages, give it the final wording rather than asking it to write the text.
6. Run an SEO check before a launch
The agent can read your metadata, headings and alt text directly. If Ahrefs or Search Console is also connected to your AI client, it can compare that with real ranking data.
Fix the list on a branch afterwards. We run this kind of check on our own site before every major content push.
Pre-merge checklist
Run this on the branch before you click merge:
The change is on the page and section you asked for, and nowhere else
Two or three similar pages still look right (shared components change everywhere)
Items you meant to keep as drafts are still drafts
Images, author and social image are set
Forms point to the right form, not one copied from another page
Mobile and tablet breakpoints look right
Links in the new content go where they should
Where Framer MCP breaks
This is what the launch posts don't cover. We have seen each of these on real client projects.
Code components. On most sites the interesting parts (heroes, carousels, calculators) are custom React code components. The agent can't change them safely. Those changes go to a developer.
Design decisions. The agent can lay out a page with your components, but it has no taste. Hierarchy, spacing and new sections still need a designer.
Shared components. Removing something that lives in a shared component on one page removes it everywhere.
Gaps get filled with what already exists. If you ask for a new form, it may wire up an old one. If you don't name an author, it may pick one.
Draft status. When CMS items are edited through Framer's API, a draft can switch back to published without warning. This is easy to miss in bulk edits.
Localization. It isn't supported in the MCP yet. Use the
@framer/agentCLI.
The pattern is consistent. Framer MCP is a strong content operator and a weak designer.
Framer MCP vs Webflow MCP
Webflow shipped its own MCP server too, so teams choosing between the two platforms ask how they compare. In day-to-day use, the difference is in the setup:
Framer MCP | Webflow MCP | |
|---|---|---|
Canvas edits | Remote, editor can be closed | Designer actions need Webflow's Bridge App open |
Review before live | Branches, then merge and publish | Staging and publish flow |
Localization | Not at launch | Supported, with limits on new localized CMS items |
Best fit | Marketing teams running content from Claude or ChatGPT | Teams already deep in Webflow's Designer |
Both servers handle content well. Neither one is a designer. We compare the platforms in more depth in Framer vs Webflow.
Troubleshooting
Problem | Fix |
|---|---|
Agent can't find your project | Paste the full project link, not the name. Check the account you connected can access it. |
Connection fails | Check the URL is exactly |
Sign-in window closed early | Re-run the connection and finish the OAuth step. |
"Not approved" or blocked | A workspace admin needs to allow MCP connections. |
Changes don't show in Framer | You're looking at main. Open the branch menu and select the newest branch. |
Live site unchanged after merge | Merging updates main only. Publish to staging, then production. |
Who should own what
Marketing team, through the agent | Your Framer partner or developer |
|---|---|
CMS items, articles, FAQs | Code components |
Featured and ordered content | Master components and design system |
Copy and legal pages | New sections and layout changes |
New pages from existing layouts | Redirects, scripts, site-wide settings |
SEO checks and metadata fixes | Localization setup |
This split is why a one to three person marketing team can keep a large Framer site current without filing a ticket for every change. If your site has to hold up through a launch, a funding round or a press cycle, that's what we set up: a Framer build an agent can run, plus a playbook like this one for your team.
Want your site set up for this?
If your Framer site was built by a freelancer, an in-house designer who has moved on, or a template, it probably isn't ready for an agent to run. We are a Framer Enterprise Partner and we build sites that marketing teams can run themselves, with or without AI.
Frequently asked questions
Is Framer MCP free?
Which AI tools work with Framer MCP?
What is the Framer MCP server URL?
Can Framer MCP publish my site?
Can Framer MCP edit code components?
When did Framer launch its MCP server?
Does the Framer editor need to be open?
How is Framer MCP different from the @framer/agent CLI?

Harish Malhi
Founder of Goodspeed
Harish Malhi is the founder of Goodspeed. He left Google in 2019 to build his own product, and started Goodspeed to give other founders the same head start. Today the studio designs and builds websites and the whole digital experience around them for funded tech companies, at the moments that matter: a raise, a launch, a press cycle. Goodspeed is a Framer Enterprise Expert, was Bubble’s Agency of the Year in 2024, and has shipped 300+ products, including launch pages for an NVIDIA-backed AI lab and a Webby-nominated site for a Boeing-backed aviation company. It holds a 5.0 rating from 46 reviews on Clutch.




