Case study

Putting a Framer site on a content pipeline with Modiva

A look at how teams use Modiva with Framer — syncing CMS collections from the tools where content actually lives, publishing the site as a pipeline step, and giving AI agents safe, scoped, revocable access — without building and maintaining a custom integration.

This is a representative example of the Modiva + Framer workflow. Have a story to share? Tell us and we’ll feature it here.

The challenge

Teams that build on Framer rarely write their content in Framer. Getting it onto the site usually means:

• Site content lived in tools like Notion, Airtable or a spreadsheet, while the site itself lived in Framer — keeping the CMS in sync meant re-typing entries by hand.
• Every content update ended with someone opening Framer just to press Publish.
• AI assistants had no way to touch the site at all — Framer offered no scoped, revocable surface to hand them.

The approach with Modiva

1. 1

   One key, one project, one connection

   The team creates a Server API key inside the Framer project and pastes it into Modiva with the project URL. The key is scoped to that single project, encrypted at rest, and revocable in one click from Framer — no OAuth app, no review queue.

2. 2

   CMS synced from where content actually lives

   An agent reads the content source (a Notion database, an Airtable base or a spreadsheet — already connected to Modiva) and writes it into a managed Framer collection through typed tools: define fields once, then add and update items on every sync.

3. 3

   Publish as the last step of the pipeline

   After a sync, the same agent calls the publish tool — Framer creates a deployment and ships it to the production hostnames. Nobody opens the editor just to press a button.

4. 4

   Site operations for AI agents via MCP

   An MCP key exposes the same tools to AI assistants: list collections, inspect fields, add items, check the last deployment. The team controls exactly which project an agent can reach, and pulling the key kills access instantly.

The outcome

• The Framer CMS mirrors the team's real content source automatically — no re-typing, no drift.
• Publishing is part of the content pipeline instead of a manual editor ritual.
• AI agents manage site content through a scoped, revocable per-project key — never shared logins.