A catalog your agent can read and install
Every theme is published as data: a manifest, both token tables, source per file, and the skills that ship inside.
bunx shadcn add https://tailthemes.com/r/foundry.jsonFoundry is free and open. The command installs its tokens, every component, every page and the agent kit, with no key and no account.
See what you getllms.txt
Two files, both live, both plain markdown, and the cheapest way to decide what to fetch.
Every theme with its price, category, pages, tags and the four URLs that address it. Free themes carry their install command inline.
The full file adds each theme's AGENTS.md verbatim, so one fetch gives you the rules before you touch the source.
curl https://tailthemes.com/llms.txtMCP server
One endpoint, streamable HTTP, stateless: one JSON-RPC message per POST, JSON back.
https://tailthemes.com/api/mcp
Protocol 2025-06-18, negotiated down to 2024-11-05 for older clients. Add it to any MCP client that speaks HTTP.
{
"mcpServers": {
"tailthemes": {
"type": "http",
"url": "https://tailthemes.com/api/mcp"
}
}
}- search_themesPublic metadata by text and category, with every URL that addresses the theme.open
- get_themeThe complete manifest including both token tables, plus AGENTS.md and README.md.open
- get_componentOne manifest-declared source file: a component, a page, theme.css, or the docs.licensed
- download_themeThe artifact for a theme. Paid slugs answer with the purchase URL instead.licensed
Metadata and token tables are open for every theme, paid ones included. Source is the product: for a paid slug get_component and download_theme answer with the price and a purchase URL. Key authentication on the connection is the next piece of work, so licensed artifacts over MCP are not served yet. Free themes are complete today.
shadcn registry
Every theme is a registry item the real shadcn CLI installs, verified against version 4.17.
bunx shadcn add https://tailthemes.com/r/foundry.json- theme.css, the whole token surface
- every section component and primitive
- every page composition
- AGENTS.md and the four skills
src/tailthemes/foundry/
Tokens are scoped to a class, never to :root, so an install cannot repaint the components you already have. Wrap the page:
<div className="tt-foundry">
For a single-theme project, copy the :root block from theme.css into your globals instead.
It answers 402 with the price, the purchase URL, the preview URL and both token tables. Only files is withheld. The shadcn CLI prints a registry's own error text on 403 and swallows it on 402, so the CLI gets 403 and the same message; every other client gets the truthful 402.
One known gap: a registry item is JSON, so image assets cannot travel with it. Themes that import images need the zip as well.
What ships inside
Your agent runs the workflows the theme brought with it, instead of reverse-engineering them.
- AGENTS.mdInvariants, the file map, and what never to be touched.
- rebrandApply a brand through tokens alone, checked against AA contrast.
- add-sectionGraft a new section using the theme's own patterns.
- add-pageCompose a page from sections that already exist.
- check-qualityRun the theme's own gate: build, responsive, a11y, token lint.
Each skill is tested in the publish gate: an agent has to complete it in a scratch copy of the theme before that theme goes live.
The kit is plain markdown, so the work continues on your machine and your own account: Claude Code, Codex, Cursor, or any agent that reads AGENTS.md. Nothing calls back here.
- listinghttps://tailthemes.com/themes/<slug>
- manifesthttps://tailthemes.com/api/themes/<slug>
- registryhttps://tailthemes.com/r/<slug>.json
- previewhttps://tailthemes.com/preview/<slug>
- artifacthttps://tailthemes.com/api/download/<slug>