Agent interface

AI tooling

Nerio exposes the same registry contract to people and agents through llms.txt and a read-only Model Context Protocol server.

MCP server

stdio

The server uses the official MCP TypeScript SDK and reads component metadata directly from the Nerio registry.

1{2  "mcpServers": {3    "nerio": {4      "command": "node",5      "args": ["packages/mcp/src/server.js"]6    }7  }8}

Read-only tools

list_componentsDiscover names, categories, and purposes.

get_componentRead the complete registry item and token contract.

get_component_usageRead usage, source files, tokens, primitives, slots, variants, and accessibility guidance.

Import model

1import { Alert, Card, Table } from "@nerio-ui/ui";2import { Button, Dialog, Select, ToastProvider } from "@nerio-ui/ui/client";3import "@nerio-ui/ui/styles.css";

Agents should keep static components on the server-safe @nerio-ui/ui entrypoint and use @nerio-ui/ui/client only for interactive Base UI-backed components.

Composition rules

Select the smallest component set that expresses the workflow.
Preserve semantic tokens, slots, and accessible names.
Use requiredTokens before inventing new product CSS variables.
Prefer source installation when a product needs to customize component behavior.
Never introduce an overlapping primitive library into a Nerio composition.

The concise machine-readable overview is available at /llms.txt.