Skip to content
easeUI Pro

Agent guide

What a coding agent needs to install easeUI Pro components on your behalf.

Token

Every request against @easeui-pro needs an EASEUI_PRO_TOKEN somewhere in the environment. An agent installing a Pro component should treat a missing token as a stop condition and ask for it, rather than skip past it or invent one. See the installation guide for where that token comes from.

Discovery

Pro doesn't have its own MCP server, installable skill, or catalog endpoint yet, the component list on /components is the source of truth for what exists and its slug. For discovering the free primitives Pro builds on, the free site's agent guide covers its MCP server and skill.

Endpoints

EndpointPurpose
/r/{slug}.jsonshadcn install item with inline file content, requires the Authorization header

Manual flow

  1. 1. Confirm the component's slug against /components, there is no discovery endpoint.
  2. 2. Fetch https://pro.easeui.dev/r/{slug}.json with an Authorization: Bearer $EASEUI_PRO_TOKEN header.
  3. 3. Write every returned file to its declared path.
  4. 4. Install anything in registryDependencies, public @easeui items, from the free registry, no token needed for those.

shadcn flow

terminal
# Registered in components.json as @easeui-pro
npx shadcn@latest add @easeui-pro/cards

# Direct registry URL, still needs the Authorization header
curl -H "Authorization: Bearer $EASEUI_PRO_TOKEN" https://pro.easeui.dev/r/cards.json