Framer Is Live in Cogny: CMS, Redirects, Analytics & Publishing for Your Agent

Framer sites are everywhere in modern marketing — landing pages, startup sites, whole company websites — and until today an agent couldn't touch one. Now it can. Framer is a live MCP integration, joining Webflow, WordPress and Ghost as the fourth CMS in the catalog.

It's also a first for the catalog under the hood: Framer ships no REST API and no official MCP server. Its official Server API (open beta since February 2026) is a WebSocket protocol driven by the official framer-api SDK against a headless instance of your project. Cogny's proxy wraps that SDK, so from your agent's side it's just thirteen ordinary MCP tools.

TL;DR

Framer is live now. Connect it with a project API key + project URL from your warehouse Settings → Cogny Managed MCPs.
Thirteen tools across four areas: CMS (list_collections, get_collection_fields, get_collection_items, add_collection_items, update_collection_item, remove_collection_items), redirects (list_redirects, add_redirects, remove_redirects), analytics (query_analytics, get_analytics_docs), and project/publishing (get_project_info, publish_site).
Nothing goes live by accident. CMS and redirect edits only reach the published site when publish_site is called, and items with draft: true are excluded from publishing entirely — so draft-first agent workflows are safe by default.
The new framer-site-signals scheduled template ships with it: weekly traffic trends, draft-backlog and content-freshness checks, redirect hygiene, and unpublished-changes alerts.
The API key is per-project — it cannot see other projects, account settings, or billing. Framer's Server API is free during its open beta.
Works from any MCP client on app.cogny.com/mcp, and from Bash via the Cogny CLI.

What you can do with it

Area	What Claude can do
CMS collections	List collections, read field schemas and items (including drafts), and batch-upsert items — one call creates or updates a whole set
Redirects	Audit the redirect table (including broken redirects whose target page was removed), add or update redirects in bulk
Site analytics	Run read-only analytics queries — visitors, page views, referrers — against Framer's built-in analytics
Publishing	Read production/staging publish state, and publish the project when a human says so

In plain terms: "Draft five case-study CMS items from this outline" — they land as drafts, keyed to the real field schema. "Which redirects are broken?" — to: null entries surface instantly. "How did traffic to the pricing page trend since the launch?" — straight from Framer's own analytics.

One honest caveat: every tool call opens a short-lived headless session of your project on Framer's side, which costs a few seconds of latency. The tools are deliberately coarse-grained — add_collection_items upserts a whole batch in one call — so agents should batch, not loop.

Draft-first by design

The write tools follow the same guardrail philosophy as the rest of Cogny. An agent can create and edit CMS items freely, but:

Draft items never publish. draft: true is the safe default for generated content.
Nothing is live until publish_site. The framer-site-signals template is explicitly forbidden from calling it — publishing is recommended in the report, decided by you.
Delete tools are flagged destructive, so MCP clients that gate destructive calls will ask first.

Two ways in: chat or scheduled

Ask interactively from any MCP client, or enable the framer-site-signals template as a scheduled prompt: it discovers your collections, pulls week-over-week traffic from Framer analytics, flags draft backlogs and stale content streams, audits redirects, and tells you when the last publish predates recent CMS edits.

Prefer the terminal? The Framer CLI page shows every tool as a npx @cogny/cli tools call one-liner an agent can script.

How to connect it

Open your project in Framer, press Cmd+K and type "open settings".
In Site Settings, find the API Keys section and create a key (name it e.g. "Cogny").
Copy the project URL from your browser address bar: framer.com/projects/<Name>--<id>.
In your warehouse Settings → Cogny Managed MCPs, click Connect on the Framer card and paste both values.

The key is stored encrypted and used only to open sessions against api.framer.com for that one project. Disconnect any time with one click. During Framer's open beta the Server API is free; Framer has said post-beta pricing will likely be usage-based — if that changes the economics, it will show up transparently in the integration's setup notes.

If your site — or your client's — runs on Framer, your agent can now do real content ops on it: drafts in, analytics out, publish only on your word. Connect it from your Cogny dashboard and ask your first question.