# Kite vs Penpot API + MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/kite-new-vs-penpot.md (~4,150 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/kite-new-vs-penpot.json · canonical https://www.anchorterminal.com/compare/kite-new-vs-penpot
- 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)

Kite scores 47 (D) on agent readiness against Penpot API + MCP's 43.7 (E), and leads in 3 of 7 scored categories. Penpot API + MCP leads on reliability and transparency & trust. Both do design files.

- Kite: D 47, rank #1039 of 1268 · https://www.anchorterminal.com/tools/kite-new.min.md
- Penpot API + MCP: E 43.7, rank #1097 of 1268 · https://www.anchorterminal.com/tools/penpot.min.md
- 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 Security & auth, 50 against 33. Also No incidents deducted, where Penpot API + MCP loses 5 points for them.
- Penpot API + MCP, good for Teams that want design files on their own servers and an agent working alongside a person in the editor. Ahead on Reliability, 46 against 33; Transparency & trust, 68 against 44. Also Open source.

| Category | Kite | Penpot API + MCP |
| --- | --- | --- |
| Reliability (16%) | 33 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 66 |
| Agent ergonomics (13%) | 44 | 41 |
| Security & auth (14%) | 50 | 33 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 76 |
| Transparency & trust (7%) | 44 | 68 |

| Fact (where they differ) | Kite | Penpot API + MCP |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Kite | Penpot (Kaleidos) |
| Hosted endpoint | `https://kite.new/api/mcp` | `https://design.penpot.app/api/rpc/command` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | Token |
| Licence | 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 | MPL-2.0 |
| Tools exposed | 59 | 5 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | `new.kite/kite` | not listed |
| Last release | 2026-11-01 | 2026-10-01 |
| Terms last updated | couldn't be read | 2025-08-05 |
| Privacy policy last updated | 2026-10-14 | 2025-08-05 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 61k stars, 1.3k npm/wk |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Transparency & trust, Penpot API + MCP +24: 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.); Penpot API + MCP 68 (MPL-2.0, including the MCP server (30). Privacy policy of 5 August 2025 names Kaleidos Subsidiary S.L., PostHog and Google Analytics, keeps data 'as long as the commercial relationship is maintained', points to a DPA in the terms and says nothing about AI training or data locations (15 of 30). Changes land in CHANGES.md, and the separate penpot-mcp repository was archived with a pointer when it moved, but there's no deprecation policy. The MCP server's move to SDK v2 removed SSE on 23 September with no changelog line we could find (8 of 20). The cloud names some processors without locations, and we didn't check self-hosted telemetry defaults (8 of 20).)
- Security & auth, Kite +17: Kite 50 (OAuth 2.1 with the authorization code flow, PKCE S256, dynamic registration of public clients, 7-day access tokens, 90-day refresh tokens that rotate on every use and revoke the connection if replayed, a revocation endpoint, bearer in the header only, and per-connection disconnect in Settings; one scope, pages, with the agent working under the user's full rights, and API keys that are per tool and revocable but unscoped (24 of 30). Least privilege comes from the file, not the token. A file shared view-only lets an agent read and comment but not draw, comment and download settings apply to agents, an agent cannot delete a file for good or touch the account, workspace or people, and each Mac-run request reaches only its file; no read-only mode on the hosted server and no confirmation for layer_remove, page_remove or version_restore (12 of 20). Comments, skills written by any editor, captured web pages and Figma pastes reach the model. The skill says a file's skills apply to that file only and never to sharing or people, and the Mac docs keep Agents Run Any Tool off by default because an agent reads comments and web pages and one could try to trick it; no guidance for the hosted server's own tools (8 of 15). Settings, Agents lists each connected app and key with when it connected and was last used, the board shows the agent's name while it works, and version history records agent saves; no per-call log for the operator (6 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001; SSO and SAML on Team (0 of 20). 24+12+8+6+0 = 50.); Penpot API + MCP 33 (Personal access tokens can expire after 30 to 180 days or never and can be deleted at any time, but carry no scopes. The hosted MCP URL takes its key in the `userToken` query parameter as the documented setup, and until 2.18.0 (23 September 2026) an MCP key also worked as a full API token, so less 10 (10 of 30). No read-only mode. `execute_code` runs arbitrary JavaScript against the plugin API, which can delete shapes, and the docs only advise starting with read-only operations. The plugin must stay open in the user's tab (5 of 20). Shared files and library content reach the model with no injection guidance (3 of 15). Audit events exist in the codebase, but we found no operator-facing call log (5 of 15). SECURITY.md routes reports through GitHub advisories, and four were published in 2026. No security.txt per the 30 September check, and no bug bounty or certification found (10 of 20).)
- Reliability, Penpot API + MCP +13: 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.); Penpot API + MCP 46 (Penpot runs as a cloud service and as self-hosted software, so this is the average of the two rubrics. Cloud (10). No status page per the 30 September check (0), so no readable incident history (5 of 30). No rate limits, 429 guidance or SLA published (0, 0, 0). The RPC API is documented and in use, while the repository's own notes call MCP multi-user mode 'under development and not yet fully integrated' (5 of 10). Self-hosted (82). Official Docker images and install guides (20). Backend, frontend, end-to-end and MCP test workflows run on push and pull request, pass state not visible (20 of 25). 706 open issues, actively labelled with milestones, and several regressions opened on 1 October are marked release blockers for 2.19.0 (15 of 25). CHANGES.md records every release, without an API versioning policy (12 of 15). Version 2.18 (15).)