cogny clicmsfirst 15 calls free

framer scripted from the shell.

Read and write Framer CMS collections, manage redirects, pull site analytics, and publish — from Bash over the Framer MCP, built on Framer’s official Server API. Content ops on a Framer site without opening the editor.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Framer toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Framer__list_collections --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Updating a Framer CMS collection means opening the project and editing items one by one in the CMS panel. The CLI upserts a whole batch of items in one call, and your site analytics come back as JSON an agent can diff week over week. Connect Framer once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Framer tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Framer tools.

Tool names as the Framer MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Framer__list_collections

List the project’s CMS collections.

cogny tools call mcp__Framer__list_collections \ --input '{}'

example response

{
  "collections": [
    {
      "id": "c1a2b3",
      "name": "Blog",
      "slugFieldName": "Title",
      "managedBy": "user"
    },
    {
      "id": "d4e5f6",
      "name": "Case Studies",
      "slugFieldName": "Client",
      "managedBy": "user"
    }
  ]
}

mcp__Framer__add_collection_items
Upsert CMS items in one batch (id = update, no id = create).
- cogny tools call mcp__Framer__add_collection_items \ --input '{"collection_id":"c1a2b3","items":[{"slug":"cli-first-content-ops","draft":true,"fieldData":{"fld_title":{"type":"string","value":"CLI-first content ops"}}}]}'
example response
```
{
  "status": "success",
  "added_or_updated": 1
}
```
mcp__Framer__query_analytics
Run a read-only analytics query against the site.
- cogny tools call mcp__Framer__query_analytics \ --input '{"query":"visitors by page","from_date":"2026-07-01","to_date":"2026-07-15"}'
example response
```
{
  "rows": [
    {
      "page": "/",
      "visitors": 4812
    },
    {
      "page": "/blog/cli-first-content-ops",
      "visitors": 903
    }
  ]
}
```

03tools list

the rest of the surface.

A sample of the other Framer tools. Run cogny tools list --json for every tool and its input schema.

mcp__Framer__get_project_info
mcp__Framer__get_collection_fields
mcp__Framer__get_collection_items
mcp__Framer__update_collection_item
mcp__Framer__remove_collection_items
mcp__Framer__list_redirects
mcp__Framer__add_redirects
mcp__Framer__remove_redirects
mcp__Framer__get_analytics_docs
mcp__Framer__publish_site

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Framer CLI or MCP?: No — Framer ships no official MCP server. This is the Cogny CLI calling Cogny’s Framer MCP over the cogny-mcp-proxy, which wraps Framer’s official Server API (the framer-api SDK). You connect a project API key + project URL once in Cogny. Framer B.V. is not affiliated.
Which Framer API does it use?: The official Framer Server API (open beta since early 2026). It has no REST endpoints — the proxy drives the official SDK against a headless instance of your project, so each call carries a few seconds of session overhead. Batch item writes into one add_collection_items call.
Do CMS edits go live immediately?: No. Item and redirect changes land in the project but only reach the live site when publish_site is called — and draft items are excluded from publishing. That makes draft-first content workflows safe by default.
What can the API key access?: Only the one project it was created in — Framer keys are per-project with no account-wide scope. Create one under Site Settings → API Keys and revoke it there any time.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

framer, then a verdict.

Start free All CLIs