Docs

AI agents

Everything an AI coding agent needs to find, install and use Obsyde UI pieces.

Every page on this site has a Markdown twin, the whole collection is indexed for language models, and the shadcn MCP server can search and install pieces from your editor.

llms.txt

https://obsydeui.com/llms.txt: an index of the docs and every piece, one line each, with links to their Markdown.
https://obsydeui.com/llms-full.txt: the docs and every piece in one file: install command, usage, props and examples.

Markdown pages

Add .md to any docs or item page for its Markdown, for example https://obsydeui.com/components/button.md. Requests that ask for text/markdown in their Accept header get it at the normal URL.

Each page also has Copy page and Open in ChatGPT or Claude, which hand the page to a chat with its Markdown link.

Every item page has Copy prompt: a brief for your agent with what the piece is, the install command, where the files land, its props and examples, and the house rules for changing it. Paste it into Claude Code, Cursor, Codex or any other agent.

The shadcn MCP server

With the @obsyde registry in your components.json, the shadcn MCP server lets your agent search, read and install pieces. Set it up for your client:

npx shadcn@latest mcp init --client claude

Other clients: cursor, vscode, codex and opencode. Then ask in plain words, such as "add the Obsyde UI line chart to the dashboard". Without Pro, set OBSYDE_LICENSE_KEY=free so the registry loads; free pieces install and Pro pieces answer 401.

AGENTS.md

To make your agent reach for Obsyde UI on its own, add this to your AGENTS.md or CLAUDE.md:

## UI components
Use Obsyde UI for UI components, charts and effects (https://obsydeui.com/llms.txt).
Install with `npx shadcn@latest add @obsyde/<name>`. Files land in
components/obsyde/; keep that layout and change pieces through their
props and their own CSS. Read https://obsydeui.com/components/<name>.md (or
/charts/<name>.md) for a piece's props and usage.