Framer MCP: The Official Way for AI Agents to Edit Your Framer Site
Framer shipped its official MCP server in late October 2026—endpoint mcp.framer.com—so Claude, Cursor, and Codex can read and modify your site directly, with review-before-publish built into the flow. Here is what it changes for design and marketing teams, and how to wire it up safely.
What Framer MCP actually gives agents
Before official MCP, asking an AI to "fix the pricing page" meant screenshots, copy-paste, and a human doing the clicking. With the server live at framer.com/mcp, an MCP-connected agent can inspect your site's structure, edit copy and sections, and stage changes for your review. Framer's launch messaging leaned hard on the safety model: agents propose, humans approve, publishing stays deliberate.
In practice this turns Framer into an agent-operable CMS for marketing sites. "Update the launch banner, fix the broken CTA on mobile, swap testimonial three" become single-prompt tasks—with a diff you check before it ships.
Setup in three steps
- Open your MCP client (Claude Desktop, Cursor, Codex) and add a new server pointing at
mcp.framer.com. - Authenticate and grant access only to the site(s) the agent should touch—least privilege applies to design tools too.
- Start with read-only asks ("audit the homepage copy"), then enable edits, and keep publishing a human step.
Framer MCP vs the alternatives
| Option | What agents touch | Best for |
|---|---|---|
| Framer MCP | Live Framer sites via MCP | Marketing sites that must change fast, with review gates |
| Figma MCP | Design files and prototypes | Design systems exploration before anything ships |
| Webflow AI | In-editor generation inside Webflow | Teams staying inside one vendor's AI features |
Pair it with these agent-stack pieces
- Mobbin MCP — feed agents real UI reference screens before they redesign your Framer sections.
- Wrenda — once the site is agent-editable, make sure GPTBot and Perplexity can actually read it.
- Agent Skills & AAIF — the portability standard context for everything MCP is converging toward.
- GitHub MCP — for teams whose sites merge code changes through PRs.
Guardrails worth keeping
Agent-editable websites concentrate risk: one over-eager prompt can restyle a revenue page. Keep change history on, restrict the agent to staging sites for experiments, require human review on pricing/legal/claim copy, and log which client and which prompt produced each change. Framer's review-before-publish default is a feature—do not route around it.
Framer MCP FAQ
What is Framer MCP?
Framer MCP is Framer's official Model Context Protocol server (endpoint mcp.framer.com). It lets AI agents like Claude, Cursor, and Codex read and edit your Framer site—changing copy, sections, and design—through a standardized, permissioned connection instead of screen-scraping or manual handoffs.
Which clients work with Framer MCP?
Any MCP client: Claude Desktop and Claude Code, Cursor, Codex, and custom agent runtimes. Connect the server URL mcp.framer.com, grant site access, and the agent can act on your project within the permissions you approve.
Can an agent publish my Framer site?
Framer emphasizes review-before-publish: agents prepare changes, humans review, then publishing happens under your control. Treat any agent-driven publishing flow with explicit approval gates.
Framer MCP vs Figma MCP vs Webflow AI?
All three target AI-assisted site/design editing. Framer MCP exposes a live Framer site to agents via MCP; Figma MCP focuses on design files; Webflow AI bakes generation into its own editor. Choose by where your site already lives.
Is Framer MCP free?
The MCP server ships with Framer—usage follows your Framer plan and site permissions. Check framer.com/mcp for current plan requirements.
AIXList is an independent AI tools directory. This article summarizes Framer's public October 2026 MCP announcement; we are not affiliated with Framer, Figma, or Webflow. Capabilities and permissions evolve—check official docs before granting site access.