# Framer Server API vs UX Pilot MCP server (slim)

> Framer Server scores 52.5 (D) to UX Pilot's 33 (F) for design canvases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framer-vs-ux-pilot-mcp.md (~4,600 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/framer-vs-ux-pilot-mcp.json · canonical https://www.anchorterminal.com/compare/framer-vs-ux-pilot-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Framer Server API: D 52.5, rank #984 of 1510 · https://www.anchorterminal.com/tools/framer.min.md
- UX Pilot MCP server: F 33, rank #1410 of 1510 · https://www.anchorterminal.com/tools/ux-pilot-mcp.min.md
- Framer Server API, good 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.
- UX Pilot MCP server, good for Designers on UX Pilot who want an agent to organise screens, review UX and build React prototypes.

| Category | Framer Server API | UX Pilot MCP server |
| --- | --- | --- |
| Reliability (16%) | 43 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 69 | 45 |
| Agent ergonomics (13%) | 47 | 46 |
| Security & auth (14%) | 49 | 39 |
| Payments & pricing (10%) | 25 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 77 | 45 |
| Transparency & trust (7%) | 75 | 22 |

| Fact (where they differ) | Framer Server API | UX Pilot MCP server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Framer | UX Pilot |
| Hosted endpoint | `https://mcp.framer.com/mcp` | `https://mcp.uxpilot.net/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | proprietary | none |
| llms.txt | yes | no |
| MCP registry | not listed | `ai.uxpilot/uxpilot` |
| Last release | 2026-10-22 | none |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 336k npm/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- 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.)