Kite vs Magic Patterns

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.

Magic Patterns 75

Hosted lines, for the MCP server and v3 API. A Statuspage at magicpatterns.statuspage.io with incident history, but its two components are Web Platform and Figma Plugin, with nothing for the API or MCP server (15 of 20). The history page and Atom feed post no incident since 9 January 2026, so the 90 days before this check are clean as far as the page covers (30). The page's /api/ path is disallowed by its robots.txt, so the JSON feeds weren't used. Rate limit published as 1,000 generations per 10 hours per key, with polling no faster than once every 60 seconds (15). No 429, Retry-After or backoff guidance and no idempotency keys. Design-system writes take a baseArtifactId and return 409 on a concurrent change, with re-read-and-retry advice (5 of 15). No SLA found below Enterprise's custom contracts (0). The MCP server and v3 API carry no beta label (10). 15 + 30 + 15 + 5 + 0 + 10 = 75.

Kite 44

MCP reading. 59 tools (61 through the Mac app) with no toolsets, read-only subset or dynamic loading; guide_read moves the long instructions out of tool descriptions into on-demand reads, but tools/list still carries 59 definitions (5 of 25). Output is sized by asking for one page in file_outline, one node in layer_source and layer_render, layer_search by name, words or type, file_search over content, comment_list with unread_only and include_resolved, request_list per file; file_list is newest-first with no documented paging (14 of 20). OAuth errors are documented with recovery steps, web_capture says when a page was cut short and an unknown shader base is refused, but a picture Kite cannot fetch is left out silently and no tool error shape is documented (9 of 20). No readOnlyHint or destructiveHint documented and no idempotency keys; version_save before a big change and version_restore undoable both ways, file_archive reversible and no permanent delete, layer_draw's replace argument for swapping a node (7 of 20). Few required parameters (file_new takes a title, layer_draw a file and HTML, finish_working a file), defaults in the drawing guide, and an MIT plugin repository for Claude Code, Codex, Cursor and Grok Bot; no SDK, since the vendor points at the official MCP SDKs (9 of 15). 5+14+9+7+9 = 44.

Magic Patterns 67

24 documented tools (15 for 11 to 30), plus 5 back for the read-only endpoint that registers only 12 (20 of 25). Message history pages by 10 and version history by 20 with skip, and file reads take a list of names (14 of 20). Documented status codes, a 402 that leaves reads working and non-blocking validationErrors on design-system writes (15 of 20). No idempotency keys; 409 conflict checks on design-system writes, and annotations couldn't be read on the closed server (10 of 20). create_design needs no parameter and makes a blank scaffold, but there is no official SDK (8 of 15). 20 + 14 + 15 + 10 + 8 = 67.

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.

Magic Patterns 84

The MCP server is closed, so its tool definitions weren't read. The v3 API has an OpenAPI 3.0.3 description, served as a block in each API reference page; the file llms.txt links at /docs/openapi-v3.yml answered with a not-found page (20 of 25). llms.txt and a Markdown copy of every docs page (10). The tools page sets out four workflows with call order, says when to poll and how often, splits read from write tools and warns that the user may edit at any time (17 of 20). Parameters are typed and marked required, the feedback category is an enum, and file writes take an array of name and content pairs (10 of 15). Request and response examples, an error table (400, 401, 402, 403) and 409 behaviour on writes (12 of 15). Versioned /v3 paths, a v2 deprecation notice and a dated product changelog (15). 20 + 10 + 17 + 10 + 12 + 15 = 84.

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.

Magic Patterns 60

Closed service under terms of service last updated 1 April 2025 (15). The privacy policy of the same date keeps personal data as long as necessary with no periods. The terms let Magic Patterns train on Free plan inputs and outputs and show Free plan designs publicly, and rule out training on paid plans. The subprocessor list sits in the Trust Center, which wasn't readable (14 of 30). No deprecation policy. v2 is 'being deprecated and will be removed in a future release' with no date, and the terms allow any part of the service to be discontinued at any time (5 of 20). The security page names Render and MongoDB Atlas as hosting, and the full subprocessor list wasn't read (8 of 20). 15 + 14 + 5 + 8 = 42.

Kite 78

Closed service with a dated changelog. The latest entry is 1 November 2026 (30). 15 dated entries between 6 October and 1 November 2026, including Pro on 18 October, Windows, shaders and website design systems on 23 October and the agent page, version, comment and export tools on 25 October (20). Support is hello@kite.new, a Support link in the docs, 'your feedback first in line' on Pro and dedicated support on Team; no community channel, forum or issue tracker, and the plugin repository has no issues (8 of 15). new.kite/kite 1.0.0 is in the official MCP registry under a DNS-verified namespace since 21 October 2026 (15). No packages to judge; the MIT plugin repository was pushed once on 7 October 2026 and the desktop apps update themselves (5 of 10). 30+20+8+15+5 = 78.

Magic Patterns 70

Changelog entry on 5 November 2026, the day before this check (30). Entries on twelve dates since 8 August, among them 23 September and 12 to 30 October (20). Closed service with a public changelog, email support within one to two business days, in-app chat and a Slack community. We didn't test them (12 of 15). Not in the official MCP registry (searches for magic-patterns and magicpatterns returned nothing of theirs). Official Claude connector, Cursor plugin and Codex plugin, and no SDKs (5 of 15). No public package or repository to check (3 of 10). 30 + 20 + 12 + 5 + 3 = 70.

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.

Magic Patterns 23

No x402, MPP or L402. A 402 means out of credits, with no payment requirements (0). Seat prices are public and the on-demand rate is $0.02 a credit, but a generation's credit cost isn't known before it runs (typical 70 per generation per the docs), so between plan-only and per-unit (15 of 20). The MCP overview and the plans table say MCP and API-key access need a paid plan, while the v3 API page says free-tier accounts can call v3 up to their credits. Taking the stricter reading for the MCP surface, the free tier gives an agent no MCP access (5 of 20). A person signs in through the browser; dynamic client registration and the device flow still end with a human approval (3 of 20). 0 + 15 + 5 + 3 = 23.