Skip to main content

MCP server and agent setup

Patine is built to be written by coding agents. Pick one or more of these; they all serve the same docs.

1. The MCP server​

@patine-ui/mcp is a tiny Model Context Protocol server with zero dependencies. It reads llms-full.txt from the patine-ui installed in your project, so answers match your version and work offline.

Claude Code:

claude mcp add patine -- npx -y @patine-ui/mcp

Cursor, Windsurf, VS Code and other clients (mcp.json):

{
"mcpServers": {
"patine": { "command": "npx", "args": ["-y", "@patine-ui/mcp"] }
}
}

It gives the agent three tools:

ToolDoes
list_componentsEvery docs page with a one-line summary
get_component_docsOne page as Markdown, e.g. { "name": "DatePicker" }: props, examples, platform notes
search_docsThe best pages for a query, e.g. "min nights date range"; then matching Pro charts, blocks and app templates, tagged Pro
search_iconsIcons in the free set (@patine-ui/icons) by name or meaning, e.g. { "query": "notification" }, then matching Pro icons and brand logos, tagged Pro

Set PATINE_DOCS=/path/to/llms-full.txt to read another copy. Without patine-ui installed it fetches this site's copy.

2. An AGENTS.md line​

Agents read AGENTS.md (or CLAUDE.md, .cursor/rules) before writing code. Add:

## UI
Build screens with patine-ui. Before writing UI code, read
node_modules/patine-ui/llms-full.txt (or use the patine MCP server) for components and props.
Use shadcn-style props: variant, size, value + onValueChange, checked + onCheckedChange.

3. The files​

FileContents
/llms.txtIndex of every page with a one-line summary
/llms-full.txtThe whole docs in one Markdown file
node_modules/patine-ui/llms-full.txtThe same, matched to your installed version
/docs/**/*.mdEach page as plain Markdown

The compact cheat sheet is on For AI assistants.

Why agents get it right​

  • Names they already know. Props follow shadcn/ui and Radix, so models have seen them thousands of times.
  • Types that fail the build. A wrong prop is a TypeScript error, not a broken screen.
  • One package, no setup. No native modules, Babel plugins or Tailwind config for the agent to get wrong.
  • Screens to copy. Pro templates use only public patine-ui exports, so an agent can adapt them line by line.