catalog_search
Search the catalog for a reusable block, contract, or template before writing one from scratch. Filters (`kind`, `templateId`, `tag`) AND together; `query` is matched against title, description, and tags. Results are the caller's own private items plus every public item, ordered by install count then recency. Returns ranked items with a short usage note each — call `catalog_install` on the id you picked, and only write from scratch when nothing fits (say so in your summary). Refuses nothing: a search that matches nothing returns an empty list.
Search the catalog for a reusable block, contract, or template before writing one from scratch. Filters (kind, templateId, tag) AND together;
Input
The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.
Calling it
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "catalog_search", "arguments": {} }
}Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.
Notes
query is matched against title, description, and tags. Results are the caller's own private items plus every public item, ordered by install count then recency. Returns ranked items with a short usage note each — call catalog_install on the id you picked, and only write from scratch when nothing fits (say so in your summary). Refuses nothing: a search that matches nothing returns an empty list.
The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.
Blocks
Search, install, and list installed. The three steps of a build's
catalog_install
Install a catalog item into one of your projects. Writes every file the item's manifest declares into the project's sandbox, then records the install against the project so a later version can update it and the install count stays accurate. Returns the files it wrote and the dependencies the item declares — it does not run the package manager, so add any `dependencies` to your project yourself, then run the project's verify step. Refuses a project you do not own, a project with no live sandbox, an item that does not exist, and another user's private item — all of those answer with a not-found that does not say which. Re-installing the same item updates it in place rather than duplicating it.