Skip to main content
modiva.ai
Sign In
← All docs

Setup guide

Connect Framer

CreativeAPI keyFramer developer docs ↗

Framer connects through the Framer Server API with a per-project API key — no OAuth app, no review queue. You create the key inside your Framer project, paste it into Modiva together with the project URL, and Modiva can then read and write managed CMS collections and items, publish and deploy the site, and read locales and code files through one unified API and MCP server. One connection maps to exactly one Framer project, and the key stays valid until you revoke it in Framer. The Server API is in open beta.

Before you start

  • A Framer project.
  • A Server API key for that project (created under the project's settings → API Keys).

Step-by-step setup

  1. 1

    Create a Server API key in Framer

    Open your project in Framer, press Cmd+K (Ctrl+K on Windows) and choose "open settings", then find the API Keys section. Create a key, label it "Modiva" and copy it — treat it like a password, since it can edit CMS content and publish the site.

  2. 2

    Sign in to Modiva

    Log in at modiva.ai and open the Dashboard. You need a Modiva account before you can connect any platform — creating one takes a minute and no credit card is required for the free tier.

  3. 3

    Open Connections → New connection

    In the left sidebar choose Connections, then click New connection. You'll see the full catalogue of platforms grouped by category (Social, Ads, CRM, E-commerce, Marketing, Creative, Productivity, Payments, Dev & Infra and Analytics).

  4. 4

    Paste the key and project URL

    Click the Framer card. In the inline form paste the API key and your project's URL (copy it from the browser while the project is open — it looks like framer.com/projects/Site--abc123), then click Connect. Modiva validates the key by reading the project's info and the connection turns green.

What Modiva can access

The key grants access to one project. CMS writes are limited to managed (API-created) collections, and the publish tool ships the live site — so review agent instructions that publish. You can revoke access any time by deleting the key in Framer or disconnecting in Modiva.

  • Read the project's info and publish state
  • Read & write managed CMS collections and items
  • Publish and deploy the site to its live hostnames
  • Read locales and code files

Troubleshooting & FAQ

Does Framer connect with OAuth or an API key?

With a per-project Server API key. Framer's Server API has no OAuth app model — you create a key inside the project and paste it into Modiva, which encrypts it at rest with AES-256-GCM. There's no app review and nothing for a workspace admin to approve.

Which collections can Modiva write to?

Writes go to managed collections — ones created through the API (for example with Modiva's collections_create tool). Collections built by hand in Framer are listed and readable, but the Server API doesn't allow writing to them. Create a managed collection and point your content sync at it.

Does publishing affect my live site?

Yes. The publish tool creates a deployment and, by default, deploys it to your production hostnames — the same as pressing Publish in Framer. Pass deploy=false to only create the deployment without shipping it.

Can I connect more than one project?

Yes — each connection covers exactly one project. Create an API key in each project you want to automate and add them as separate connections.

Do Framer API keys expire?

No. The key stays valid until you delete it in the project's API Keys settings, so there's no token refresh — the connection stays healthy until you revoke it.

How do I disconnect?

Open Connections, click the Framer row and choose Disconnect — Modiva deletes the stored key immediately. Also delete the "Modiva" key in your Framer project's API Keys settings to fully revoke access.

Need help with Framer?

Reach the team any time from our support page, or ask Fin, our AI support agent.