u/appelton

After playing with FRAMER 3.0 inside my CLAUDE CODE for the past few days, I just want to say big .....THANK YOU to the entire team. The amount of crazy difficult work that I can now do with entire Agent Implementation is absolutely insane.

Things that were not possible before are now being done as if it is no big deal.

THANK YOU !!

Thayil says there could “potentially be more than nine” tracks, but with no specific timetable for the finished product.

>— Kim Thayil

“We’re still working,” he says. “I still have things to do. So does Ben. There’s no schedule here, because it’s a different process. When you work on a record, you have both time and money budgeted out by the record company in concert with the band and management. But because this production doesn’t have a traditional schedule, it’s kind of sideways — in some ways backward and some ways forward.

I've been building a custom MCP server (Model Context Protocol)

that exposes the entire Framer Plugin SDK 3.10.x to AI agents

After two months of building, I've hit a wall that no amount of

clever code can solve. The Plugin SDK is missing critical APIs

that turn what should be 30 seconds of automation into 30 minutes

of clicking.

__________________

## What's missing

**1. Variables API**

There is no programmatic way to:

- Create project Variables (string, color, number, boolean)

- Read or list existing Variables

- Update Variable values

Variables are foundational for CMS-driven design. Without an API,

every variable for every component must be created by hand

through the UI panel.

____________________

**2. Property Controls → Variables binding API**

When a component has 30+ property controls (real example: a

pricing card with Variant, Status, Plan Name, Description,

Features 1-7, Show Feature 1-7 booleans, 4 armor metrics),

binding each to a Variable requires:

- Click property control

- Right-click → "Connect to Variable"

- Select variable from dropdown

- Repeat 30 times

This is not automatable through the SDK. There is no

`setBinding(nodeId, propKey, variableId)` method.

____________________

**3. Variables → CMS field binding API**

Same problem at the next layer. After variables exist and

properties are bound, you still need to bind each variable to a

CMS collection field through the UI. No SDK method exists.

____________________

**4. Page → CMS collection binding API**

Setting a page like `/products/:slug` to bind to a CMS collection

must be done through Page Settings UI. The SDK silently rejects

`:slug` placeholders in `setAttributes` link attribute. No

`setPageCollectionBinding(pageId, collectionId)` method exists.

____________________

**5. Cross-collection lookup binding API**

For binding a component property to "the field X of the item in

collection Y where slug equals current page slug" — only

achievable through the multi-step UI workflow:

Filter → Slug Equals → Value → Set Variable → current page Slug.

Cannot be set through SDK.

____________________

## Why this matters

The current SDK lets plugins read CMS content, manipulate

canvas nodes, and set basic properties. But it cannot wire the

data layer to the presentation layer programmatically. That

wiring is exactly what makes Framer powerful for content sites —

and it's the part that completely blocks plugin-driven

automation.

Real impact for our use case:

- 9 collections, 35 fields each, ~50 components per page

- Manual binding: ~8 hours per page template

- With proper SDK: ~5 minutes per page template

We're looking at hundreds of hours of UI clicking that should

be one script.

____________________

## FRAMER SDK TEAM

1. Is Variables API on any roadmap? Even read-only access wouldhelp.
2. Can binding setters (`setPropertyBinding`,`setVariableCmsBinding`, `setPageCollectionBinding`) be added?
3. Is there a reason these are intentionally UI-only, or is thisjust a gap that hasn't been prioritized?

The Server API (framer-api package) is great for reads and

publishing, but doesn't address these structural gaps either.

Anyone else hitting these limits? What workarounds are you

using?