# Framer Server API vs Kite (slim)

> Framer Server scores 52.6 (D) to Kite's 47 (D) for design files. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framer-vs-kite-new.md (~4,550 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/framer-vs-kite-new.json · canonical https://www.anchorterminal.com/compare/framer-vs-kite-new
- 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-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Framer Server API scores 52.6 (D) on agent readiness against Kite's 47 (D), and leads in 4 of 7 scored categories. Kite leads on payments & pricing. Both do design files.

- Framer Server API: D 52.6, rank #894 of 1268 · https://www.anchorterminal.com/tools/framer.min.md
- Kite: D 47, rank #1039 of 1268 · https://www.anchorterminal.com/tools/kite-new.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 33; Schema & documentation, 69 against 62; Transparency & trust, 75 against 44.
- Kite, good for Agents that make banners, social posts, landing pages and screens for a team that will edit and comment on them in a shared file, drawing in HTML and CSS against the team's design system and picking up changes from @-mention comments, without a desktop app or browser tab kept open. Ahead on Payments & pricing, 30 against 25. Also Free to start without a card.

| Category | Framer Server API | Kite |
| --- | --- | --- |
| Reliability (16%) | 43 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 69 | 62 |
| Agent ergonomics (13%) | 47 | 44 |
| Security & auth (14%) | 50 | 50 |
| Payments & pricing (10%) | 25 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 77 | 78 |
| Transparency & trust (7%) | 75 | 44 |

| Fact (where they differ) | Framer Server API | Kite |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | Framer | Kite |
| Hosted endpoint | `https://mcp.framer.com/mcp` | `https://kite.new/api/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Licence | proprietary | Proprietary hosted service under Kite's terms of use (updated 8 September 2026). No source is published; the only public code is an MIT plugin manifest repository (itsloukman/kite-agent-plugins) that points agents at the hosted server |
| Tools exposed | none | 59 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `new.kite/kite` |
| Last release | 2026-10-22 | 2026-11-01 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | 2026-10-14 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 336k npm/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Transparency & trust, Framer Server API +31: 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).); Kite 44 (Closed service. The terms of use (8 September 2026) run to about 200 words on content, prohibited use, links, availability and changes and name no legal entity, address or governing law, so the contracting party is unknown (8 of 30). The privacy policy (14 October 2026) names eight services, says files are not read, trained on or sold, discloses masked session replays and error replays, gives the agent token's 7-day life renewable to 90 days (matching auth.md and the integration page), the 30-day purge of deleted pages and the one-month deletion of a closed account's files, and the Figma token's handling; no DPA and no retention period for logs beyond the providers' own (20 of 30). No deprecation policy or dated notices; the terms promise email or in-app notice of changes that matter and the changelog dates additions, not removals (4 of 20). Telemetry (PostHog, Sentry) is disclosed with what it excludes and no opt-out beyond product-news emails; service locations are given only for PostHog and Sentry (US) (10 of 20). 8+20+4+10 = 42.)
- Reliability, Framer Server API +10: Framer Server API 43 (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 shows 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 (20 of 30). 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). 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).); Kite 33 (Hosted reading, for the platform and its remote MCP server. No public status page was found. None is linked from the docs or the footer, https://kite.new/status answers 404 and status.kite.new does not resolve (0). No readable incident history, so the floor (5). Limits are published with numbers on the account page, 200 agent actions a day on Free, reset at midnight UTC, unlimited on Pro; 60 new files an hour; 20 comments on one file every 10 minutes; 600 exported layers an hour; 20 keys; file caps of 400 MB and 250,000 layers. auth.md says registration and agent calls are rate-limited without a per-minute figure (12 of 15). 429 is documented in auth.md with 'back off' and no Retry-After, 401 with a refresh-once-then-rediscover rule, and the drawing guide says to edit layers in place rather than redraw; no idempotency key on any write and no safe-retry guidance for layer_draw, so a retried draw adds a second frame (6 of 15). No SLA. The terms (8 September 2026) say Kite is provided as is, uptime is not guaranteed and files may be lost (0). The hosted server carries no beta label and the registry entry is 1.0.0; the product launched on 6 October 2026 and the desktop apps are 0.1.16 (10). 0+5+12+6+0+10 = 33.)
- Schema & documentation, Framer Server API +7: 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.); Kite 62 (MCP reading, since the MCP server is the only surface an outside agent reaches. No tool input schemas were read. The server card at /.well-known/mcp/server-card.json declares tools without listing them, and llms-full.txt describes every tool in prose with argument names in the skill, so typed inputs are the vendor's to show and were not seen (10 of 25). llms.txt, llms-full.txt, skill.md, auth.md and pricing.md are served as text and Markdown (10). Descriptions say what each tool does and when to use it, such as file_search over file_list when the user describes a file, layer_edit rather than redrawing, never base64 in HTML, never a picture of a design, guide_read's six topics, and the view-only rule (16 of 20). Inputs named in the docs are typed in prose, with enumerations for audience (link, restricted), export formats (svg, react, tailwind, html), sticky colours, shader bases and guide topics, and bounds for videos (100 MB) and fonts (4 MB), but the main write tool takes one HTML string and layer_edit a free CSS object (8 of 15). Worked HTML examples in skill.md, a prompt per client page, and auth.md's 401, 400 and 429 responses; no example tool call or response and no MCP error shape (8 of 15). A dated changelog with 15 entries from 6 October to 1 November 2026 that names agent-facing changes (page, version, comment and export tools on 25 October), server version 1.0.0; no versioned tool surface or deprecation policy (10 of 15). 10+10+16+8+8+10 = 62.)
- Payments & pricing, Kite +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).); Kite 30 (No x402, MPP or L402 in the docs, llms.txt, auth.md, the pricing pages or the terms (0). Plan prices are public and machine-readable at pricing.md, Free, Pro $20 per editor a month or $16 yearly, Team $35 or $28, with no per-call or per-action price since agent actions are counted on Free and unlimited on Pro (10 of 20). Free plan with 3 files and 200 agent actions a day, sign-up by emailed link or Google, no card mentioned anywhere (20). An agent can register itself as an OAuth client, but a person must sign up in a browser and click Allow, or make an API key in Settings (0). 0+10+20+0 = 30.)