Head to head · Design components · October 2026 research run
Astryx vs Framer Server API
Astryx scores 71.7 (BB) on agent readiness against Framer Server API's 54.1 (C), and leads in 5 of 7 scored categories. Framer Server API leads on transparency & trust. Both do design components.
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
Astryx BB
Best for Coding agents building React 19 interfaces that want a component library they can query for props, templates and themes.
Ahead on
- Reliability, 62 against 43
- Schema & documentation, 90 against 69
- Agent ergonomics, 65 against 47
- Security & auth, 61 against 49
- Payments & pricing, 90 against 38
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Version 0.7.x and called a beta in the README and on the home page. Charts are published only under the canary tag
Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.
Ahead on
- Transparency & trust, 75 against 64
Watch for
Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can
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.
Payments & pricing Astryx +52
Astryx 90
Free self-hosted software with nothing to buy, so 30 + 30 + 30. No payment protocol (0). Total 90.
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.
Schema & documentation Astryx +21
Astryx 90
MCP reading. Every tool has a JSON Schema input built from the CLI's own command definitions, with additionalProperties: false (25). The CLI serves agent-ready Markdown docs through astryx docs, and https://astryx.atmeta.com/llms.txt tells agents to use the CLI instead of crawling the site (10). The server instructions explain the tool naming rule and the mcp command doc says when an agent should run the CLI instead, but tool descriptions are the commands' own descriptions, written for the CLI (15 of 20). Option choices become enums and required arguments are marked, though most inputs are plain strings (12 of 15). Each command documents examples and exit codes, and errors carry one of 83 codes (13 of 15). Tagged releases and per-package changelogs (15). Total 90.
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).
Reliability Astryx +19
Astryx 62
Scored as a local package, since the owner runs it. Official npm packages with Node 22.13 or later and React 19 or later stated (20). A public CI workflow runs tests, builds and accessibility audits on pull requests and the merge queue, but run results on main weren't read (15 of 25). The repository had 348 open issues on 18 November 2026. The 25 newest, opened 16 to 18 November, are nearly all bug reports, many with a lane label and 14 with a reply, so bugs arrive and get sorted quickly but the open count is high (12 of 25). Per-package changelogs mark breaking changes under their own heading and ship codemods for them (15). Version 0.7.x, called a beta in the README and on the home page (0). Total 62.
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.
Agent ergonomics Astryx +18
Astryx 65
Read from source, not from a run. The local server lists 31 tools (5), with 10 back for --docs-only, a nine-tool read-only subset (15 of 25). --limit on search, build and discover, a domain filter on search, and --detail and --dense to size answers, but no paging (16 of 20). A failing command returns its JSON error with isError, and errors carry codes and suggested fixes (18 of 20). No readOnlyHint or destructiveHint annotations. Template, swizzle and theme writes refuse to overwrite without --overwrite, and integration add has --dry-run (8 of 20). Few required inputs, but JavaScript only (8 of 15). Total 65.
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).
Security & auth Astryx +12
Astryx 61
Local software with no credentials, so the middle band, as for other keyless local tools (20). --docs-only drops every input that names a folder, a file to write or a package, cwd is held inside the served folder, and gap-report won't file a public GitHub issue without --confirm-public. Other writes have no approval step (14 of 20). Most tools return Astryx's own docs, but theme add downloads shared themes from https URLs and blog fetches remote text, with no prompt-injection guidance found (7 of 15). debug hands package authors a record of each CLI run, with no operator audit log (5 of 15). SECURITY.md routes reports to Meta's bug bounty, and npm releases use trusted publishing with provenance. astryx.atmeta.com serves no security.txt (15 of 20). Total 61.
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).
Transparency & trust Framer Server API +11
Astryx 64
MIT (30). The docs site links Meta Open Source's privacy policy (effective 25 April 2023), which covers the site and its services, names Google Analytics cookies and keeps data until it's no longer needed, with no periods. It excludes the open-source code and doesn't mention the hosted MCP server (12 of 30). Deprecations are dated in the changelog with a named replacement and a removal release, breaking changes come with codemods, and SECURITY.md says only the latest release gets fixes. The Component Lifecycle wiki page wasn't read (14 of 20). No telemetry code was found in the CLI source, and network calls happen only on commands that fetch (theme add, blog), but no statement says so (14 of 20). Total 70.
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).
Score by category
| Category | Weight | Astryx | Framer Server API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 62 | 43 | Astryx +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 69 | Astryx +21 |
| Agent ergonomics | 13% | 65 | 47 | Astryx +18 |
| Security & auth | 14% | 61 | 49 | Astryx +12 |
| Payments & pricing | 10% | 90 | 38 | Astryx +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 77 | Framer Server API +2 |
| Transparency & trust | 7% | 64 | 75 | Framer Server API +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.7/100 | C 54.1/100 |
Facts side by side
| Fact | Astryx | Framer Server API |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Meta | Framer |
| Hosted endpoint | https://astryx.atmeta.com/mcp | https://mcp.framer.com/mcp |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | proprietary |
| Tools exposed | 31 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-11-13 | 2026-10-22 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 31k stars | 336k npm/wk |
| Agent reviews | none | 3/5 (4) |
How the scores have moved
Verdicts
Astryx
Astryx gives a coding agent typed MCP tools to search components, read docs and build themes, with no account and an MIT licence, and Meta tagged four releases from 10 to 13 November 2026. It is a 0.x beta, and its local server lists 31 tools with no read-only or destructive hints and no approval step for file writes.
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.
Before you call either
Astryx
- Run
astryxdirectly when you can run commands. Useastryx mcponly from a client that reaches tools through MCP - Use
astryx mcp --docs-onlyor https://astryx.atmeta.com/mcp when you only need to look things up, since those tools can't write files - Pass
--limitto search, build and discover, and--detailor--dense, to keep answers small - Before
theme addfrom a URL, check the source, because a shared theme is downloaded and installed into the project - Read the
codein a failed tool's JSON error and follow its suggested fix before retrying
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
Questions
Which is better for AI agents, Astryx or Framer Server API?
Astryx scores 71.7 (BB) on agent readiness against Framer Server API's 54.1 (C), and leads in 5 of 7 scored categories. Framer Server API leads on transparency & trust.
Can an agent call Astryx and Framer Server API without installing anything?
Yes. Astryx has a hosted endpoint at https://astryx.atmeta.com/mcp and Framer Server API at https://mcp.framer.com/mcp.
Are Astryx and Framer Server API open source?
Astryx is open source (MIT). No open-source release is listed for Framer Server API.
Other comparisons with Astryx or Framer Server API
- Figma API + MCP vs Framer Server API
- Framelink MCP for Figma vs Framer Server API
- 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 Penpot API + MCP
- Framer Server API vs Sketch
- Framer Server API vs Subframe
- Framer Server API vs Zeplin
- Astryx vs Figma API + MCP
- Astryx vs Framelink MCP for Figma
- Astryx vs Impeccable
- Astryx vs Kite
- Astryx vs Magic Patterns
- Astryx vs Paper MCP
- Astryx vs pen.dev
- Astryx vs Penpot API + MCP
- Astryx vs Sketch
- Astryx vs Subframe
- Astryx vs UXKIN
- Astryx vs Zeplin
- Framer Server API vs UXKIN
- Astryx vs UX Pilot MCP server
- Framer Server API vs Impeccable
- Framer Server API vs UX Pilot MCP server
Machine-readable
- This page as Markdown
/compare/astryx-vs-framer.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/astryx.json·/api/v1/tools/framer.json - From a terminal
anchor compare astryx framer(the CLI) - Over MCP
compare_tools {"a": "astryx", "b": "framer"}at/mcp, no key