Claude + Framer: What the Integration Can (and Can't) Do in 2026
There’s no official Claude Framer connector in Anthropic’s directory — but Framer shipped its own Server API in February 2026, and a marketplace MCP plugin already wires Claude straight into your open project. That combination makes Claude + Framer genuinely useful today. Framer never appeared in Anthropic’s Connectors Directory, so you won’t find a one-click toggle in Claude’s settings. What you’ll use instead is one of three real routes: the community Framer MCP plugin, Framer’s brand-new Server API, or the older Plugin/CMS API for in-editor automation.
Here’s each route, when to pick it, and what to use when you want Framer work that happens without you at the keyboard.
Route 1: The Framer MCP plugin (Marketplace)
The closest thing to a real Claude ↔ Framer link is the MCP plugin on the Framer Marketplace (published by Tommy D. Rossi). It runs a Model Context Protocol server endpoint out of your open Framer project and exposes it to any MCP-compatible client — Claude Desktop, Cursor, and others — over a secure tunnel.
Once connected, Claude can:
- Read your project structure — an XML representation of pages, components, and code files.
- Work with the current selection — read and manipulate the nodes you have selected on the canvas.
- Update text and color styles, search fonts, and run node operations.
- Export components as React and manage code files.
In practice you can say “rewrite this landing section’s copy for the SEO brief I pasted,” “make a countdown-timer code component,” or “update the brand color across these styles,” and Claude works against the live project. The plugin ships free and, like Framer’s other AI features, is available on every plan including Free. The tradeoff: it only runs while Framer is open with the plugin active — it’s an in-editor bridge, not a background service.
Route 2: Framer’s Server API
On February 12, 2026, Framer launched the Server API — programmatic access to a Framer project “from any server at any time, without opening the Framer project from a client.” This is the route to reach for when you want automation that doesn’t depend on the editor being open.
The Server API mirrors the Plugin API’s capabilities: sync CMS collections with external sources like Notion or Airtable, publish changes, update the canvas, and change project settings. Framer positions it for exactly this kind of work — triggered by “AI agents, webhooks, or scheduled jobs” and “ideal for batch processing and LLM integrations.” Framer’s own docs even walk through building “a little MCP server that can update your website from your company Slack,” so wrapping it as a custom MCP endpoint for Claude is an intended pattern, not a hack.
To wire it up:
- In Framer, open site settings and create an API key.
- Install the
framer-apinpm package and script against it (a stateful WebSocket channel handles fast streaming, and it interoperates with REST and webhooks). - Expose your script as a small MCP server, or just call it from Claude Code, so Claude can drive real Framer changes.
Note it’s free during open beta — good for building now, but a beta, so expect changes.
Route 3: The Plugin API and CMS API
If you’re building inside Framer rather than from a server, the Plugin API (and its CMS API) is the mature path. Plugins can read and write the Framer CMS, and a 2026 update lets them reach all collections, not just plugin-created ones — enough to generate an entire blog post and write it straight into the CMS. Recent additions include a createManagedCollection method, Gallery-field support, and a Code File API for managing code components and overrides.
You’d have Claude help you write a plugin (it’s good at TypeScript against a documented API), but the plugin itself runs client-side inside an open Framer tab. It’s the right tool for interactive, in-editor automation — and the same capability set the Server API now offers headlessly.
Worth knowing: Framer has its own AI already — Workshop (describe a component in natural language, get a working code-based one), Wireframer (generate a responsive layout from a prompt), and Auto Rename, all on every plan. For a lot of design tasks you may not need Claude in the loop at all.
The limits that actually matter
- No official Anthropic connector. Framer isn’t in the Connectors Directory, so there’s no one-click Claude toggle — you’re assembling the MCP plugin or the Server API yourself.
- No triggers. MCP tools and Claude Code run inside a session you start. Nothing watches your Framer site or CMS and acts when a form is submitted, an item is published, or a scheduled job is due.
- Not event-driven. The MCP plugin needs Framer open; Claude Code needs your machine on. The closest “runs on its own” option fires on a preset timer rather than in response to a design change or anything else that happens — and it has no inbox of its own to receive work.
- claude.ai on the web can’t reach a local setup. The Marketplace MCP plugin and any local server live on your machine; the web app can’t see them.
- Server API is open beta. Free now, but subject to change.
Claude + Framer is excellent for “help me build and edit this project right now.” It’s not built for “watch my site and act when something happens.”
If you want Framer work that runs on its own: Carly
The moment you want something to fire without you in a session — the instant a form comes in, on a schedule, when a CMS item changes — you’ve crossed past what Claude is for.
Carly reaches Framer through your own Framer Server API key (paste it on the integrations page) — one of 200+ native integrations plus anything with an API. It’s built to act on triggers, 24/7, in the cloud:
- When a form is submitted on your Framer site, Carly adds the lead to your CRM and emails a personalized reply.
- On a schedule, Carly syncs new items from Notion or Airtable into your Framer CMS and publishes.
- When you drop a request in Slack, Carly updates copy on the right CMS collection and pushes it live.
- No-code setup — tell Carly “follow up with every form submission and keep my CMS in sync,” in plain English. It interviews you, then builds the workflow with you. No prompt engineering.
- Actually sends — drafts and sends email through Gmail and Outlook, with attachments and labels.
- Connects to anything — 200+ native integrations across 40+ categories, plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (MCP plugin / Server API) | Carly | |
|---|---|---|
| Read & search a Framer project | Yes | Yes |
| Edit content and styles in a session | Yes | Yes |
| Acts on triggers / events | No | Yes |
| Syncs & publishes on a schedule | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Monitors form submissions on its own | No | Yes |
| Sends email as part of the flow | No | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best hands-on Framer building assistant; Carly is the teammate that keeps your Framer site running while you’re away.
Frequently Asked Questions
Does Claude work with Framer?
Yes, through unofficial routes. There’s no Anthropic directory connector for Framer, but the Framer Marketplace MCP plugin exposes your open project to Claude, and Framer’s Server API (launched February 2026) lets Claude Code or a custom MCP server make real changes programmatically.
Is there an official Framer MCP server?
Not a first-party one from Framer. Framer ships the Server API (open beta, free) and even documents building your own MCP server on top of it. For an out-of-the-box bridge, the community MCP plugin on the Framer Marketplace runs an MCP endpoint from your open project.
Can claude.ai on the web access Framer?
No. The Marketplace MCP plugin and any Server API wrapper run locally or on your own server, which the claude.ai web app can’t reach. You’ll use Claude Desktop or Claude Code for those routes.
Can Claude publish my Framer site or sync the CMS automatically?
Not on its own. Claude acts inside a session you start — there are no triggers or schedules. For automatic form follow-ups, scheduled CMS syncs, and publishing on events, use an agent platform like Carly. AI agents start at $35/month.
More: Claude connectors · Claude + Webflow · Claude + Figma · Can Claude send emails · Claude vs Carly · Integrations
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
