# Astryx vs Penpot API + MCP

> Astryx scores 71.7 (BB) to Penpot's 35.8 (F) for design components. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/astryx-vs-penpot
- Markdown: https://www.anchorterminal.com/compare/astryx-vs-penpot.md (~4,850 tokens)
- Slim: https://www.anchorterminal.com/compare/astryx-vs-penpot.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/astryx-vs-penpot.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Astryx scores 71.7 (BB) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on transparency & trust. Both do design components.

- Astryx: grade BB, 71.7/100, rank #260 of 1557. Markdown https://www.anchorterminal.com/tools/astryx.md · JSON https://www.anchorterminal.com/api/v1/tools/astryx.json
- Penpot API + MCP: grade F, 35.8/100, rank #1429 of 1557. Markdown https://www.anchorterminal.com/tools/penpot.md · JSON https://www.anchorterminal.com/api/v1/tools/penpot.json
- Best design workspace and canvas APIs for AI agents: https://www.anchorterminal.com/best/design/index.md
- All 162 design comparisons: https://www.anchorterminal.com/compare/design/index.md

## Which one, for what

### Astryx (BB)

Good 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 44
- Schema & documentation, 90 against 66
- Agent ergonomics, 65 against 41
- Security & auth, 61 against 35
- Payments & pricing, 90 against 45

Also in its favour:
- Agent-ready, a grade of BB or better
- No key needed to call it
- Runs on your own machine
- No incidents deducted, where Penpot API + MCP loses 15 points for them

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

### Penpot API + MCP (F)

Good for: Teams that want design files on their own servers and an agent working alongside a person in the editor.

Ahead on:
- Transparency & trust, 71 against 64

Also in its favour:
- Free to start without a card

Watch for: Personal access tokens have no scopes, and the hosted MCP key goes in a URL query string


## Why the edge

### Payments & pricing: Astryx +45

- Astryx (90): Free self-hosted software with nothing to buy, so 30 + 30 + 30. No payment protocol (0). Total 90.
- 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.

### Security & auth: Astryx +26

- 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.
- 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).

### Schema & documentation: Astryx +24

- 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.
- Penpot API + MCP (66): The integration guide links generated API docs at design.penpot.app/api/_doc, and the backend's page template at 2.18.6 links a Swagger/OpenAPI description, but design.penpot.app's robots.txt disallows /api/ for every crawler, so neither page can be read and neither counts here. Every MCP tool in @penpot/mcp declares a typed zod input schema (read from the source at 2.18.6), which meets the line for MCP (25). No llms.txt (help.penpot.app/llms.txt answered 404 on 5 November). The MCP server's `high_level_overview` and `penpot_api_info` tools hand the model its docs instead (3 of 10). RPC docs are generated with little prose. MCP descriptions are long and tell the model to read the overview before `execute_code` (12 of 20). RPC inputs are typed, but the main MCP tool takes one JavaScript string (9 of 15). A curl example for `get-profile`. No documented error format, and the integration guide still says 'we do not have any specific documentation for the webhooks yet' (5 of 15). CHANGES.md per release (12 of 15).

### Agent ergonomics: Astryx +24

- 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.
- 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).

### Reliability: Astryx +18

- 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.
- Penpot API + MCP (44): Penpot runs as a cloud service and as self-hosted software, so this is the mean of the two rubrics, rounded half away from zero. Cloud (10). No status page was found on 5 November (0), so no readable incident history (5 of 30). No numeric rate limit, 429 guidance or SLA is published for the cloud. The terms define fair use only as no more than 10 times the median data usage (0, 0, 0). The RPC API is documented and in use, while MCP multi-user mode was described as under development per the 1 October check, not re-read on 5 November (5 of 10). Self-hosted (77). Official Docker images and install guides (20). Backend, frontend, common, end-to-end, exporter, library, MCP, plugins and WASM test workflows run in public GitHub Actions, and the pass state can't be read without github.com, so 15 of 25 by this run's reading (was 20). 706 open issues, labelled with milestones, per the 1 October check, not re-read on 5 November (15 of 25). CHANGES.md records every release, without an API versioning policy (12 of 15). Version 2.18 (15). (10 + 77) / 2 = 43.5, so 44.

### Transparency & trust: Penpot API + MCP +7

- 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.
- Penpot API + MCP (71): MPL-2.0, including the MCP server (30). The privacy policy, last updated 5 August 2025 and now served at /privacy-policy, names Kaleidos, 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, but there's no deprecation policy. The removal of legacy SSE from the MCP server is now listed under the unreleased 2.19.0 heading, and released 2.18.6 still serves /sse (8 of 20). Self-hosted telemetry is off by default and documented as an opt-in flag (`enable-telemetries`) in the configuration guide (read from the docs source in the repository clone), which meets the line for the self-hosted half (20). The cloud names some processors without locations (8). (20 + 8) / 2 = 14 of 20.

## Score by category

| Category | Weight | Astryx | Penpot API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 62 | 44 | Astryx +18 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 66 | Astryx +24 |
| Agent ergonomics | 13% | 65 | 41 | Astryx +24 |
| Security & auth | 14% | 61 | 35 | Astryx +26 |
| Payments & pricing | 10% | 90 | 45 | Astryx +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 76 | Penpot API + MCP +1 |
| Transparency & trust | 7% | 64 | 71 | Penpot API + MCP +7 |
| Negative events | ≤15 | 0 | -15 | |
| **Total** | | **71.7 · BB** | **35.8 · F** | |

## Facts side by side

| Fact | Astryx | Penpot API + MCP |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | Meta | Penpot (Kaleidos) |
| Hosted endpoint | `https://astryx.atmeta.com/mcp` | `https://design.penpot.app/api/rpc/command` |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | None | Token |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | MPL-2.0 |
| Tools exposed | 31 | 5 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-11-13 | 2026-11-04 |
| Terms last updated | no document linked | 2025-08-05 |
| Privacy policy last updated | no document linked | 2025-08-05 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 31k stars | 61k stars |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### Astryx

- +4.0 on 18 November 2026 (B to BB): new evidence

### Penpot API + MCP

- +1.9 on 13 November 2026: checklist
- -9.8 on 5 November 2026 (E to F): security, new evidence, correction
- +0.2 on 27 October 2026: checklist

## 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.

**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

### Astryx

1. Run `astryx` directly when you can run commands. Use `astryx mcp` only from a client that reaches tools through MCP
2. Use `astryx mcp --docs-only` or https://astryx.atmeta.com/mcp when you only need to look things up, since those tools can't write files
3. Pass `--limit` to search, build and discover, and `--detail` or `--dense`, to keep answers small
4. Before `theme add` from a URL, check the source, because a shared theme is downloaded and installed into the project
5. Read the `code` in a failed tool's JSON error and follow its suggested fix before retrying

### Penpot API + MCP

1. Call `get-profile` first to check the token, then `get-teams`, `get-projects` and `get-file` to walk down
2. Ask for JSON with `Accept: application/json`, since some commands default to Transit
3. Call `high_level_overview` and `penpot_api_info` before `execute_code`. They tell the model what the plugin API can do
4. Keep the Penpot tab in the foreground. A backgrounded or frozen tab stalls MCP calls
5. 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, Astryx or Penpot API + MCP?

Astryx scores 71.7 (BB) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on transparency & trust.

### Can an agent call Astryx and Penpot API + MCP without installing anything?

Yes. Astryx has a hosted endpoint at https://astryx.atmeta.com/mcp and Penpot API + MCP at https://design.penpot.app/api/rpc/command.

### Are Astryx and Penpot API + MCP open source?

Yes. Astryx is open source (MIT). Penpot API + MCP is open source (MPL-2.0).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/astryx-vs-penpot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/astryx-vs-penpot.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "astryx", "b": "penpot"}`. From a terminal: `anchor compare astryx penpot`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/astryx.json and https://www.anchorterminal.com/api/v1/tools/penpot.json

## Other comparisons with Astryx or Penpot API + MCP

- [Figma API + MCP vs Penpot API + MCP](https://www.anchorterminal.com/compare/figma-mcp-vs-penpot.md)
- [Framelink MCP for Figma vs Penpot API + MCP](https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-penpot.md)
- [Framer Server API vs Penpot API + MCP](https://www.anchorterminal.com/compare/framer-vs-penpot.md)
- [Kite vs Penpot API + MCP](https://www.anchorterminal.com/compare/kite-new-vs-penpot.md)
- [Miro API + MCP vs Penpot API + MCP](https://www.anchorterminal.com/compare/miro-vs-penpot.md)
- [pen.dev vs Penpot API + MCP](https://www.anchorterminal.com/compare/pen-dev-vs-penpot.md)
- [Penpot API + MCP vs Sketch](https://www.anchorterminal.com/compare/penpot-vs-sketch.md)
- [Penpot API + MCP vs Subframe](https://www.anchorterminal.com/compare/penpot-vs-subframe.md)
- [Penpot API + MCP vs Zeplin](https://www.anchorterminal.com/compare/penpot-vs-zeplin.md)
- [Astryx vs Figma API + MCP](https://www.anchorterminal.com/compare/astryx-vs-figma-mcp.md)
- [Astryx vs Framelink MCP for Figma](https://www.anchorterminal.com/compare/astryx-vs-framelink-figma-mcp.md)
- [Astryx vs Framer Server API](https://www.anchorterminal.com/compare/astryx-vs-framer.md)
- [Astryx vs Impeccable](https://www.anchorterminal.com/compare/astryx-vs-impeccable.md)
- [Astryx vs Kite](https://www.anchorterminal.com/compare/astryx-vs-kite-new.md)
- [Astryx vs Magic Patterns](https://www.anchorterminal.com/compare/astryx-vs-magic-patterns.md)
- [Astryx vs Paper MCP](https://www.anchorterminal.com/compare/astryx-vs-paper-mcp.md)
- [Astryx vs pen.dev](https://www.anchorterminal.com/compare/astryx-vs-pen-dev.md)
- [Astryx vs Sketch](https://www.anchorterminal.com/compare/astryx-vs-sketch.md)
- [Astryx vs Subframe](https://www.anchorterminal.com/compare/astryx-vs-subframe.md)
- [Astryx vs UXKIN](https://www.anchorterminal.com/compare/astryx-vs-uxkin-agent.md)
- [Astryx vs Zeplin](https://www.anchorterminal.com/compare/astryx-vs-zeplin.md)
- [Penpot API + MCP vs UXKIN](https://www.anchorterminal.com/compare/penpot-vs-uxkin-agent.md)
- [Astryx vs UX Pilot MCP server](https://www.anchorterminal.com/compare/astryx-vs-ux-pilot-mcp.md)
- [Impeccable vs Penpot API + MCP](https://www.anchorterminal.com/compare/impeccable-vs-penpot.md)
- [Magic Patterns vs Penpot API + MCP](https://www.anchorterminal.com/compare/magic-patterns-vs-penpot.md)
- [Melius vs Penpot API + MCP](https://www.anchorterminal.com/compare/melius-vs-penpot.md)
- [Paper MCP vs Penpot API + MCP](https://www.anchorterminal.com/compare/paper-mcp-vs-penpot.md)
- [Penpot API + MCP vs UX Pilot MCP server](https://www.anchorterminal.com/compare/penpot-vs-ux-pilot-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
