Docs / MCP
Point your agent at the catalogue
ui.artbloom speaks the Model Context Protocol. Connect any MCP client and it can search every template, block, component and animation here — then read a piece's exact install command and source — without a key or an account.
Server endpoint
https://ui.artbloom.tech/mcpAdd it to your client
Every MCP client takes the same endpoint — three of the common ones, verbatim.
Claude Code
claude mcp add --transport http artbloom https://ui.artbloom.tech/mcpCursor, Windsurf, VS Code
{
"mcpServers": {
"artbloom": {
"url": "https://ui.artbloom.tech/mcp"
}
}
}Claude Desktop, or any stdio-only client
{
"mcpServers": {
"artbloom": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ui.artbloom.tech/mcp"]
}
}
}mcp-remote bridges the HTTP endpoint to clients that only speak stdio. Nothing to install first — npx fetches it.
The two tools
The server is deliberately small. It reads the same registry the site and CLI read, so an agent never sees a piece the catalogue doesn’t ship.
search_registry
Find pieces by free text and, optionally, by kind — templates, blocks, components or animations. Returns each match’s name, kind and one-line description: enough to choose, not the whole payload.
get_item
Read one piece by name: its install command, the exact files it writes with their sizes, the npm packages it needs, and — only when asked — the full source. This is what lets an agent install something and know what landed.
Both are read-only. There is nothing the server can change in your project, and nothing it needs to know about you — no key, no account, no rate-limited sign-up.
Verify it’s live
The endpoint is POST-only, so a browser visit shows nothing. One request lists the tools:
curl -sX POST https://ui.artbloom.tech/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'