Tool: Astryx for agents (CLI and MCP server)

What it does

• A command-line tool and a remote MCP server that let an AI look up Astryx components, templates and props instead of guessing.
• Astryx says its API, docs and CLI are designed so a person and an AI build the same way.

When to reach for it

• An agent is building on Astryx.
• The agent keeps inventing props or writing raw divs.
• You're handing the site to someone whose own AI will keep changing it.

How to use it

• Always use the scoped name @astryxdesign/cli. The bare astryx package on npm is unrelated.
• npx @astryxdesign/cli init writes the component list into your AGENTS.md or CLAUDE.md.
• Lookups: search, docs, component <Name>, component --list.
• The three-step workflow it teaches the agent:
  1. build "<idea>" picks a template;
  2. template sets it up;
  3. component reads the props.
• template --cdn writes a no-build HTML page pinned to your installed version.
• The rules it gives the agent: start every page from a template, no raw divs, no style={{}}, tokens instead of made-up values.
• MCP server: claude mcp add --transport http astryx https://astryx.atmeta.com/mcp. It offers search(query) and get(name).
• A global CLI install keeps one Astryx skill at ~/.agents/skills/astryx/SKILL.md, linked into agent skill folders.
• --detail brief and --dense shorten the output for pasting into a chat AI.
• Add a package.json script alias so agents don't guess the CLI's path.
• The docs site's llms.txt tells agents to use the CLI instead of crawling pages.

What happened when we used it

Not used here yet.

Source

• Source: Astryx.