Feature request: Inbox/Self-driving - Framer MCP support

Feature request

Title:
Feature request: Inbox/Self-driving - Framer MCP support

Is your feature request related to a problem?

From: 62303 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/62948):

"Inbox PR - Framer MCP

Framer has recently launched 'Framer 3.0' which brings full integrated Framer AI and branching, enabling full AI design of pages, components, CMS, SEO, etc.

Further, their MCP also allows to engage with this functionality through integration with major AI providers and Slack etc.

Curious - With the prevalence of no-code platforms, perhaps integrating Framer MCP into your Inbox and allowing for PH agents to create 'branches' and design/webpages changes on Framer?"

Sites built on no-code platforms like Framer have no GitHub repo, so inbox agents have nothing to act on, because self-driving currently relies a GitHub repo to push PRs to.

Describe the solution you'd like

Is your feature request related to a problem?

Self-driving assumes a GitHub repo: setup requires one, and the deliverable is a PR. Sites built on no-code platforms like Framer have no repo, so inbox agents have nothing to act on.

Describe the solution you'd like

Framer 3.0 shipped git-style branching and an MCP server for external agents. Let inbox agents also propose changes as Framer branches, the way they propose GitHub PRs today.

Describe alternatives you've considered

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/62303 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/62948)

Debug info

Start by reviewing the Inbox/self-driving setup and its current GitHub repository and PR workflow, which the issue identifies as the existing entry point. Then investigate how Framer's MCP server and branching could fit that workflow; done means agents can propose Framer branch changes as an alternative to GitHub pull requests.