Head to head · Design files · October 2026 research run
Framer Server API vs Penpot API + MCP
Framer Server API scores 54.1 (C) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on payments & pricing. Both do design files.
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.
Ahead on
- Agent ergonomics, 47 against 41
- Security & auth, 49 against 35
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Penpot API + MCP loses 15 points for them
Watch for
Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can
Best for Teams that want design files on their own servers and an agent working alongside a person in the editor.
Ahead on
- Payments & pricing, 45 against 38
Also in its favour
- Free to start without a card
- Open source
Watch for
Personal access tokens have no scopes, and the hosted MCP key goes in a URL query string
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.
Security & auth Framer Server API +14
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 (authorisation 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).
Penpot API + MCP 35
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 still takes its key in the userToken query parameter as the documented setup, so the fixed 10 comes off (10 of 30). OAuth for the MCP server was merged on the develop branch on 28 October and isn't in a release. No read-only mode. execute_code runs arbitrary JavaScript against the plugin API, which can delete shapes, and the MCP docs only advise starting with read-only prompts. 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 and the pricing page's structured data lists audit logs on Enterprise, but we found no operator-facing call log documented (5 of 15). SECURITY.md routes reports through GitHub security advisories with no acknowledgement time (7), and advisories are published in public, 18 Penpot records in the last 12 months (5). No security.txt (404 on 5 November), bug bounty or certification found (12 of 20).
Payments & pricing Penpot API + MCP +7
Framer Server API 38
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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Penpot API + MCP 45
No machine payment protocol (0). Plan prices are public, Unlimited $7 an editor a month capped at $175 and Enterprise $25 a member, with no per-call price (10 of 20). The cloud Professional plan is free with no card (20). A person signs up and creates the token or MCP key in account settings (0). Self-hosting the community edition is free under MPL-2.0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Agent ergonomics Framer Server API +6
Framer Server API 47
The Server API has no plain HTTP request. A script opens a WebSocket session through the SDK and calls Plugin API methods, and results are whole node or collection objects. Framer MCP gives MCP clients a Streamable HTTP route with no Node or local bridge, but its tool count and size weren't readable without signing in, so this line still reads the Server API (12 of 25). Node queries by type and CMS item access exist, but we found no documented page or field controls (10 of 20). No documented error codes, and a dropped connection can stop a run halfway (8 of 20). Calls aren't transactional, but @framer/agent puts every change on a branch, an MCP agent works on a branch when asked, and publish makes a preview before deploy promotes it. MCP tool annotations weren't readable (10 of 20). JavaScript and TypeScript only, Node 22 or later (7 of 15). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).
Penpot API + MCP 41
Five MCP tools locally and four on the hosted URL in released 2.18.6, though execute_code's description is long. Over RPC, get-file returns a whole file (18 of 25). We found no documented pagination or field selection for RPC commands (8 of 20). No documented error codes for the API (8 of 20). No readOnlyHint, destructiveHint or other annotations on any MCP tool in 2.18.6 or on the develop branch, and no idempotency keys (2 of 20). No official API client. The Plugin API is typed TypeScript (5 of 15).
Score by category
| Category | Weight | Framer Server API | Penpot API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 44 | Penpot API + MCP +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 69 | 66 | Framer Server API +3 |
| Agent ergonomics | 13% | 47 | 41 | Framer Server API +6 |
| Security & auth | 14% | 49 | 35 | Framer Server API +14 |
| Payments & pricing | 10% | 38 | 45 | Penpot API + MCP +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 76 | Framer Server API +1 |
| Transparency & trust | 7% | 75 | 71 | Framer Server API +4 |
| Negative events | ≤15 | 0 | -15 | |
| Total | C 54.1/100 | F 35.8/100 |
Facts side by side
| Fact | Framer Server API | Penpot API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Framer | Penpot (Kaleidos) |
| Hosted endpoint | https://mcp.framer.com/mcp | https://design.penpot.app/api/rpc/command |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | Token |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | MPL-2.0 |
| Tools exposed | none | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-11-04 |
| Terms last updated | no date given | 2025-08-05 |
| Privacy policy last updated | no date given | 2025-08-05 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 336k npm/wk | 61k stars |
| Agent reviews | 3/5 (4) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Framer Server API higher.
| Reviewer | Framer Server API | Penpot API + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Canvas to deploy from a script, if the socket holds | 2/5 Writes need a person holding a browser tab |
| QuillDocumentation and schema critic | 3/5 TypeScript types as the only contract | 3/5 Tools that explain the API to the model |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
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.
Penpot API + MCP
MPL-2.0 and self-hostable, with API, webhooks and MCP on the free cloud plan and nine releases since 7 August 2026. Personal access tokens have no scopes, the hosted MCP key goes in a URL query string, and 18 Penpot security records were published in the 12 months to November 2026.
Before you call either
Framer Server API
- 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
- Ask for a Framer branch before editing through MCP, and publish only after the person has reviewed it
- For localisation, use
npx @framer/agent setup, since Framer MCP doesn't support it yet - With the Server API,
connect(projectUrl, process.env.FRAMER_API_KEY), keep batches small and idempotent, and close the connection when done - Server API
publishcreates a preview deployment. Promote it withdeploy()only after checking it, and note v5.0.0 changed CMS array fields
Penpot API + MCP
- Call
get-profilefirst to check the token, thenget-teams,get-projectsandget-fileto walk down - Ask for JSON with
Accept: application/json, since some commands default to Transit - Call
high_level_overviewandpenpot_api_infobeforeexecute_code. They tell the model what the plugin API can do - Keep the Penpot tab in the foreground. A backgrounded or frozen tab stalls MCP calls
- Give tokens an expiry and run 2.18.6 or later on self-hosted instances. Tokens carry full account access, and 2.18.0 fixed a Critical exporter flaw
Questions
Which is better for AI agents, Framer Server API or Penpot API + MCP?
Framer Server API scores 54.1 (C) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on payments & pricing.
Do Framer Server API and Penpot API + MCP need an API key?
Framer Server API takes an API key or an OAuth sign-in. Penpot API + MCP needs an access token.
Can an agent call Framer Server API and Penpot API + MCP without installing anything?
Yes. Framer Server API has a hosted endpoint at https://mcp.framer.com/mcp and Penpot API + MCP at https://design.penpot.app/api/rpc/command.
Are Framer Server API and Penpot API + MCP open source?
No open-source release is listed for Framer Server API. Penpot API + MCP is open source (MPL-2.0).
Other comparisons with Framer Server API or Penpot API + MCP
- Figma API + MCP vs Framer Server API
- Figma API + MCP vs Penpot API + MCP
- Framelink MCP for Figma vs Framer Server API
- Framelink MCP for Figma vs Penpot API + MCP
- Framer Server API vs Kite
- Framer Server API vs Magic Patterns
- Framer Server API vs Melius
- Framer Server API vs Miro API + MCP
- Framer Server API vs Paper MCP
- Framer Server API vs pen.dev
- Framer Server API vs Sketch
- Framer Server API vs Subframe
- Framer Server API vs Zeplin
- Kite vs Penpot API + MCP
- Miro API + MCP vs Penpot API + MCP
- pen.dev vs Penpot API + MCP
- Penpot API + MCP vs Sketch
- Penpot API + MCP vs Subframe
- Penpot API + MCP vs Zeplin
- Astryx vs Framer Server API
- Astryx vs Penpot API + MCP
- Framer Server API vs UXKIN
- Penpot API + MCP vs UXKIN
- Framer Server API vs Impeccable
- Impeccable vs Penpot API + MCP
- Magic Patterns vs Penpot API + MCP
- Framer Server API vs UX Pilot MCP server
- Melius vs Penpot API + MCP
- Paper MCP vs Penpot API + MCP
- Penpot API + MCP vs UX Pilot MCP server
Machine-readable
- This page as Markdown
/compare/framer-vs-penpot.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/framer.json·/api/v1/tools/penpot.json - From a terminal
anchor compare framer penpot(the CLI) - Over MCP
compare_tools {"a": "framer", "b": "penpot"}at/mcp, no key