Connect the Framer API

• ✓ CMS collections & items
• ✓ Publishing
• ✓ Locales & code files
• ✓ Token expiry
• — Webhooks (Poll via the collection/item tools)

project_

info · publish · deploy

collections_

list · create · fields get/set

items_

list · add · remove

locales_

list

code_files_

list

OAuth scopes requested

• Read your project info and publish state
• Read & write managed CMS collections and items
• Publish and deploy your site
• Read locales and code files

# Add Modiva's MCP server to your agent
{
  "mcpServers": {
    "modiva": {
      "url": "https://mcp.modiva.ai",
      "headers": { "Authorization": "Bearer $MODIVA_MCP_KEY" }
    }
  }
}

# Then connect Framer and call its tools, e.g.
accounts_list(provider="framer")

How do I connect the Framer API with Modiva?

Create a Modiva account, generate an MCP key, and connect Framer from your dashboard. Modiva runs the full OAuth flow and stores the encrypted token for you — no client secrets in your code.

What can I do with the Framer API through Modiva?

Sync CMS collections and items, publish your site, and read locales and code files on your Framer projects through one unified API and MCP server. You get 12 typed tools grouped by resource (project_, collections_, items_, locales_, code_files_), callable over REST or the MCP server.

Do I need to handle OAuth or token refresh myself?

No. Modiva handles the Framer OAuth handshake, token storage (envelope-encrypted) and automatic refresh. You call a single unified endpoint.

Can an AI agent use the Framer API?

Yes — that is the point. Modiva exposes Framer as Model Context Protocol (MCP) tools, so agents like Claude, Cursor or your own app can read and act on Framer through one endpoint.