Head to head · Design code · October 2026 research run

Astryx vs UX Pilot MCP server

Astryx scores 71.7 (BB) on agent readiness against UX Pilot MCP server's 34.2 (F), and leads in every scored category. Both do design code.

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 15
  • Schema & documentation, 90 against 45
  • Agent ergonomics, 65 against 46
  • Security & auth, 61 against 39
  • Payments & pricing, 90 against 30
  • Maintenance & community, 75 against 45
  • Transparency & trust, 64 against 22

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

UX Pilot MCP server F

Best for Designers on UX Pilot who want an agent to organise screens, review UX and build React prototypes.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, limits or error docs

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 +60

Astryx 90

Free self-hosted software with nothing to buy, so 30 + 30 + 30. No payment protocol (0). Total 90.

UX Pilot MCP server 30

No machine payment protocol (0). Pricing behind script, not read (0). Free tier (20). A person signs up (0). 0 + 0 + 20 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Astryx +47

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.

UX Pilot MCP server 15

No status page found (0). No history (5). No limits found (0). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.

Schema & documentation Astryx +45

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.

UX Pilot MCP server 45

Schemas not read without sign-in (15 of 25). No llms.txt read (0). Tools grouped by job (find, organise, delete, import, review, React), with a help tool that maps old names to new calls (14 of 20). Inputs not verifiable (5 of 15). A tool that returns any action's fields with an example (8 of 15). Registry 3.0.0 on 4 November; no changelog (3 of 15). 15 + 0 + 14 + 5 + 8 + 3 = 45.

Transparency & trust Astryx +42

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.

UX Pilot MCP server 22

Terms and privacy render with script and weren't readable (0). Data handling not read (0). A tool that maps old tool names to new calls eased the 3.0 change, no dates (5 of 20). Subprocessors not found (0). 0 + 0 + 5 + 0 = 5.

Maintenance & community Astryx +30

Astryx 75

v0.7.16 tagged on 13 November 2026, five days before this check, with commits on main on 18 November (30). Five or more releases in the last 90 days, including v0.7.10 on 6 November and v0.7.13 to v0.7.16 from 10 to 13 November (20). 348 open issues and 704 open pull requests on 18 November. Of the 25 newest issues, opened 16 to 18 November, 14 had a reply and many carried a lane label (15 of 25). No Astryx entry in the official MCP registry, searched for astryx and astryxdesign on 18 November (0 of 15). Dependabot, a pinned pnpm lockfile and CI workflows (10). Total 75.

UX Pilot MCP server 45

Registry 3.0.0 and repository on 4 November 2026 (30). Dated releases not found (0). Issues not read (0). Official registry entry ai.uxpilot/uxpilot (15). README-only repository (0). 30 + 0 + 0 + 15 + 0 = 45. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Security & auth Astryx +22

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.

UX Pilot MCP server 39

OAuth or a bearer key; scopes not published (20 of 30). Organise tools never delete, and deletes need confirmation (14 of 20). Imported AI output and comments are third-party text; no injection guidance (3 of 15). No audit log (0). No security programme found (2 of 20). 20 + 14 + 3 + 0 + 2 = 39.

Score by category

CategoryWeightAstryxUX Pilot MCP serverEdge
Reliability16%6215Astryx +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9045Astryx +45
Agent ergonomics13%6546Astryx +19
Security & auth14%6139Astryx +22
Payments & pricing10%9030Astryx +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7545Astryx +30
Transparency & trust7%6422Astryx +42
Negative events≤1500
TotalBB 71.7/100F 34.2/100

Facts side by side

FactAstryxUX Pilot MCP server
KindSDK + MCPMCP server
VendorMetaUX Pilot
Hosted endpointhttps://astryx.atmeta.com/mcphttps://mcp.uxpilot.net/mcp
Transportsstdio, Streamable HTTPStreamable HTTP
AuthNoneOAuth
PricingFreeFreemium
x402nono
LicenceMITnone
Tools exposed31none
Read-only variant documentedyesno
llms.txtyesno
MCP registrynot listedai.uxpilot/uxpilot
Last release2026-11-13none
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity31k starsnone

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.

UX Pilot MCP server

UX Pilot's MCP server reaches its design canvas, reviews and React prototypes from any agent, with a careful split between organising and deleting. Little else is public, no status page, limits, errors or readable legal pages.

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

UX Pilot MCP server

  1. Ask the help tool for an action's fields before calling it
  2. Delete only after the user confirms
  3. Treat imported AI output and comments as untrusted

Questions

Which is better for AI agents, Astryx or UX Pilot MCP server?

Astryx scores 71.7 (BB) on agent readiness against UX Pilot MCP server's 34.2 (F), and leads in every scored category.

Can an agent call Astryx and UX Pilot MCP server without installing anything?

Yes. Astryx has a hosted endpoint at https://astryx.atmeta.com/mcp and UX Pilot MCP server at https://mcp.uxpilot.net/mcp.

Are Astryx and UX Pilot MCP server open source?

Astryx is open source (MIT). No open-source release is listed for UX Pilot MCP server.

Other comparisons with Astryx or UX Pilot MCP server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.