Head to head · Design canvases · October 2026 research run

Framer Server API vs UX Pilot MCP server

Framer Server API scores 52.5 (D) on agent readiness against UX Pilot MCP server's 33 (F), and leads in every scored category. Both do design canvases.

Best design workspace and canvas APIs for AI agents · All 133 design comparisons

Which one, for what

Framer Server API D

Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.

Ahead on

  • Reliability, 43 against 15
  • Schema & documentation, 69 against 45
  • Security & auth, 49 against 39
  • Payments & pricing, 25 against 20
  • Maintenance & community, 77 against 45
  • Transparency & trust, 75 against 22

Watch for

Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can

UX Pilot MCP server F

Best for Designers on UX Pilot who want an agent to organise screens, review UX and build React prototypes.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, limits or error docs

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Framer Server API +53

Framer Server API 75

Closed service under published terms, version 1.8 effective 16 June 2026, whose definition of the Service excludes Framer APIs. framer-api is MIT on npm, and @framer/agent 0.0.47 declares no licence (18 of 30). Privacy statement version 1.7 of 12 June 2026 names Framer B.V., gives retention periods (transaction data 7 years, account data up to 2 years after closure) and links a DPA. Its AI line only covers training 'third-party general-purpose AI models' on personal data (22 of 30). Breaking changes are flagged by major version, such as the v4.0.0 package rename and v5.0.0 CMS array fields, with no deprecation policy or notice period. The External Agents page is now labelled legacy and stays supported 'while Framer MCP reaches feature parity', with no end date (8 of 20). Transfer countries are listed in the Trust Center per the privacy statement. We didn't confirm a subprocessor list (10 of 20). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).

UX Pilot MCP server 22

Terms and privacy render with script and weren't readable (0). Data handling not read (0). A tool that maps old tool names to new calls eased the 3.0 change, no dates (5 of 20). Subprocessors not found (0). 0 + 0 + 5 + 0 = 5.

Maintenance & community Framer Server API +32

Framer Server API 77

Per the 24 October check, not re-read on 4 November, Framer MCP was published on 22 October 2026, and Plugin API v5.1.0 and framer-api 5.1.0 on npm on 24 September (30). In the 90 days from 6 August, v5.0.0 (8 September), v5.1.0 (24 September), @framer/agent 0.0.47 (15 October, per the 24 October npm reading) and the Framer MCP release (22 October) are four dated entries; v4.1.0 (4 August) has left the window (20). Closed service with a public changelog, an updates page and a community forum. We didn't test support (10 of 15). Presence of Framer MCP in the official MCP registry wasn't established; the 24 October search used the registry's JSON API, which this check doesn't use (0). One official SDK, now at the Plugin API's version (10 of 15). framer-api 5.1.0 declares Node 22 or later and two runtime dependencies (7 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.

UX Pilot MCP server 45

Registry 3.0.0 and repository on 4 November 2026 (30). Dated releases not found (0). Issues not read (0). Official registry entry ai.uxpilot/uxpilot (15). README-only repository (0). 30 + 0 + 0 + 15 + 0 = 45. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Reliability Framer Server API +28

Framer Server API 43

Per the 24 October check, not re-read on 4 November, Framer runs a Better Stack status page at framerstatus.com with App, Editor, API, Hosting, Sites, Website and Community components, and no component for Framer MCP (20). Its RSS feed showed three incidents in the 90 days to 24 October 2026, analytics collection degraded at a third-party provider for about 1 hour 15 minutes on 12 August, elevated errors in the AI tools for 1 hour 15 minutes on 22 September and the Editor unavailable for 39 minutes on 14 October, with the API component at 100 per cent over 30 days. Minor only. 25 October to 4 November is unread and gets no credit of its own (20 of 30, kept). No rate limits published for the Server API or Framer MCP (0). No 429 or retry guidance. The FAQ says the API 'is not in any way transactional' and scripts must handle partial failures themselves (3 of 15, partial kept). No SLA published. The Enterprise plan lists an 'Uptime guarantee' without published terms (0). The Server API is in open beta and Framer MCP is labelled preview on the pricing page (0 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.

UX Pilot MCP server 15

No status page found (0). No history (5). No limits found (0). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.

Schema & documentation Framer Server API +24

Framer Server API 69

No OpenAPI or REST contract. The Server API's contract is the TypeScript types in the framer-api SDK over a WebSocket (12 of 25). llms.txt at framer.com, re-read on 24 October (10). The Plugin API reference documents each method, and @framer/agent installs skills that tell coding agents how to use it (12 of 20). Typed TypeScript inputs with union types for node and field kinds (12 of 15). Quick-start examples and a REST-wrapper example on GitHub. No error reference found (8 of 15). A dated changelog with semver and breaking changes flagged, v4.1.0 on 4 August, v5.0.0 on 8 September and v5.1.0 on 24 September 2026, and a dated updates page that announced Framer MCP on 22 October (15). Framer doesn't publish Framer MCP's tool definitions and listing them needs an OAuth sign-in, so this score still reads the Server API. Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).

UX Pilot MCP server 45

Schemas not read without sign-in (15 of 25). No llms.txt read (0). Tools grouped by job (find, organise, delete, import, review, React), with a help tool that maps old names to new calls (14 of 20). Inputs not verifiable (5 of 15). A tool that returns any action's fields with an example (8 of 15). Registry 3.0.0 on 4 November; no changelog (3 of 15). 15 + 0 + 14 + 5 + 8 + 3 = 45.

Security & auth Framer Server API +10

Framer Server API 49

One Server API key per project, created under Site Settings, that can't reach other projects. We didn't find rotation or revocation documented for Server API keys. @framer/agent grants access per project in the browser and Framer says it can be revoked at any time. Framer MCP signs in with OAuth (authorization code with PKCE S256 and dynamic client registration, per its metadata), but publishes one scope, mcp:project, and acts with the account's permissions on every project it can reach, so it doesn't earn the 30 for scoped OAuth. Revoking an MCP grant isn't documented in the pages read (20 of 30). No read-only key or MCP mode. The key can publish and deploy directly. @framer/agent keeps changes on a branch until someone merges or publishes, and MCP changes stay unpublished until the person or the agent publishes (12 of 20). CMS content and code files come back as they are, mostly the customer's own, with no injection guidance (5 of 15). We found no API or MCP call log for operators (5 of 15). Per the 24 October check, framer.com's security.txt lists vulnerability-disclosure@framer.com and carries an expired Expires date of 1 August 2026. trust.framer.com redirects to a Vanta page whose robots.txt disallows crawlers, so certifications weren't checked. A disclosure address with no acknowledgement time, bounty or readable certification takes the run's settled 7 (7 of 20). Not re-read on 4 November (framer.com paused under its Acceptable Use Policy).

UX Pilot MCP server 39

OAuth or a bearer key; scopes not published (20 of 30). Organise tools never delete, and deletes need confirmation (14 of 20). Imported AI output and comments are third-party text; no injection guidance (3 of 15). No audit log (0). No security programme found (2 of 20). 20 + 14 + 3 + 0 + 2 = 39.

Payments & pricing Framer Server API +5

Framer Server API 25

No machine payment protocol (0). The Server API is free during beta and Framer says it'll 'likely charge for this API on a per-use basis, with a monthly free allowance', with no price set. The pricing page lists the MCP Server as 'Free during preview' with no later price. Site plans are public (5 of 20). Free on every plan, including the Free site plan, during the Server API beta and the MCP preview (20). A person creates the key in Site Settings, approves @framer/agent in a browser or signs in to Framer to approve an MCP client. Dynamic client registration registers the client, not an account (0). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).

UX Pilot MCP server 20

No machine payment protocol (0). Pricing behind script, not read (0). Free tier (20). A person signs up (0). 0 + 0 + 20 + 0 = 20.

Score by category

CategoryWeight this runFramer Server APIUX Pilot MCP serverEdge
Reliability16%204315Framer Server API +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26945Framer Server API +24
Agent ergonomics13%16.24746Framer Server API +1
Security & auth14%17.54939Framer Server API +10
Payments & pricing10%12.52520Framer Server API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87745Framer Server API +32
Transparency & trust7%8.87522Framer Server API +53
Negative events≤1500
TotalD 52.5/100F 33/100

Facts side by side

FactFramer Server APIUX Pilot MCP server
KindHTTP APIMCP server
VendorFramerUX Pilot
Hosted endpointhttps://mcp.framer.com/mcphttps://mcp.uxpilot.net/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
Licenceproprietarynone
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedai.uxpilot/uxpilot
Last release2026-10-22none
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity336k npm/wknone
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Framer Server API

Framer's remote MCP server and the Server API both reach the canvas, components, code files and CMS, and nothing goes live until someone publishes. Both are pre-release, with no published rate limits, post-preview price or SLA. MCP sign-in has one scope covering every project the account can reach, and Server API keys can publish with no read-only option.

UX Pilot MCP server

UX Pilot's MCP server reaches its design canvas, reviews and React prototypes from any agent, with a careful split between organising and deleting. Little else is public, no status page, limits, errors or readable legal pages.

Before you call either

Framer Server API

  1. Add https://mcp.framer.com/mcp as a Streamable HTTP server and sign in to Framer in the browser. Give the agent the full project link, not the project name
  2. Ask for a Framer branch before editing through MCP, and publish only after the person has reviewed it
  3. For localisation, use npx @framer/agent setup, since Framer MCP doesn't support it yet
  4. With the Server API, connect(projectUrl, process.env.FRAMER_API_KEY), keep batches small and idempotent, and close the connection when done
  5. Server API publish creates a preview deployment. Promote it with deploy() only after checking it, and note v5.0.0 changed CMS array fields

UX Pilot MCP server

  1. Ask the help tool for an action's fields before calling it
  2. Delete only after the user confirms
  3. Treat imported AI output and comments as untrusted

Questions

Which is better for AI agents, Framer Server API or UX Pilot MCP server?

Framer Server API scores 52.5 (D) on agent readiness against UX Pilot MCP server's 33 (F), and leads in every scored category.

Do Framer Server API and UX Pilot MCP server need an API key?

Framer Server API takes an API key or an OAuth sign-in. UX Pilot MCP server uses an OAuth sign-in.

Can an agent call Framer Server API and UX Pilot MCP server without installing anything?

Yes. Framer Server API has a hosted endpoint at https://mcp.framer.com/mcp and UX Pilot MCP server at https://mcp.uxpilot.net/mcp.

Other comparisons with Framer Server API or UX Pilot MCP server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.