Creativity · MCP — server

MCP Framer Server

The MCP Framer Server wraps Framer's API for sites and CMS collections, letting Claude list pages, read components, update CMS entries, and trigger publishes. It fits the vibe-coding and AI-native-marketing workflows popular in 2026, where content teams iterate on a landing page entirely through chat.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript
Transports: stdio

Capabilities

Tools: list_pages, update_cms_entry, create_cms_entry, publish_site
Resources: framer://site/{id}/page/{slug}, framer://collection/{id}/entry/{id}
Auth: Framer API personal access token

Install

npx -y @community/mcp-server-framer

Configuration

{
  "mcpServers": {
    "framer": {
      "command": "npx",
      "args": ["-y", "@community/mcp-server-framer"],
      "env": {
        "FRAMER_TOKEN": "${FRAMER_TOKEN}",
        "FRAMER_WORKSPACE": "${FRAMER_WORKSPACE}"
      }
    }
  }
}

Frequently asked questions

What kind of sites can it edit?

Any Framer site whose workspace the API token belongs to. CMS collections are the safest surface — structural page changes usually still happen in the Framer editor.

Can it deploy a preview?

Yes. The publish_site tool triggers a build and deploy; most clients gate this behind explicit user confirmation.

How is it different from a CMS MCP like Sanity?

Framer couples design + content + hosting. It's ideal when the LLM should preview on a real URL immediately. Sanity separates content from rendering and suits polyglot frontends.

Sources

Framer Developer docs — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20
MCP servers repo — accessed 2026-04-20