Connect
Add Minerals to your agent once. After that it works in two ways.
- You ask. Say ‘add a component library’ or ‘add a carousel’. Your agent asks Minerals and shows you up to three choices. You pick one.
- It offers. When your agent is about to build something Minerals has a fit for, it offers that in one line: Yes or Not now. At most once per session.
On a yes, your agent pulls it straight from its maker. Nothing is added without your yes. A yes for a whole listing is kept in the project’s minerals.json and covers its other items.
Install
Claude Code
claude mcp add --scope user --transport http minerals https://minerals.dev/mcpCursor
Under mcpServers in ~/.cursor/mcp.json, merged into the existing file:
"minerals": { "url": "https://minerals.dev/mcp" }Codex
codex mcp add minerals --url https://minerals.dev/mcpAny other client
A remote MCP server over Streamable HTTP, with no sign-in:
https://minerals.dev/mcpMaking your install key… The keyless address https://minerals.dev/mcp always works too.
The repo line
One sentence for a repo’s agent instructions (CLAUDE.md, AGENTS.md, Cursor rules), so agents working there ask by default.
For design libraries, components, assets, effects and references, ask Minerals first: https://minerals.dev/mcpOther ways
Claude Code plugin
claude plugin marketplace add Mineralsdev/minerals
claude plugin install minerals@mineralsSkills
npx skills add Mineralsdev/mineralsshadcn
npx shadcn@latest add Mineralsdev/minerals/connectThe five MCP tools
What your agent can call. find_design is the front door; the other four follow from its answers.
find_design: Searches the Minerals shelf of design libraries and tools.get_listing: Returns the pull for a ref from find_design.report_outcome: Records that what get_listing returned was not used after all.offer: Gives the exact words for one choice, Yes or Not now, about one free item or one listing.suggest_listing: Sends a proposal for a design library or tool to the Minerals curator.
What is logged
- Searches: the words of the need, the filters, which listings were shown, the number of refs the project already has, and which path asked (for example, the install guide’s first run).
- Site search: the words typed into the site’s own search box, and which listings matched.
- Handoffs: which listing an agent asked the pull for, and the client name it gave.
- Offers: which listing or item was offered, the answer, and the install key if there was one.
- Click-outs: which listing was clicked through to, and the page it came from.
- Reports: that an agent said it did not use a listing, and its reason if it gave one.
- Pulls: which item was pulled, the client or tool that fetched it, and the install key if there was one.
- Requests: the host of a suggested link. The request itself is kept apart from the log.
- Arrivals: that the server’s address was opened by a plain request. Nothing else.
- Guide reads: that the install guide was read, and the install key if its address carried one.
- Quiet failures: that a call was answered late or failed, and which tool it was.
- Failed sign-ins to the back office: the time only.
- Project labels: the stack names, project type and stage an agent sent.
- An install key, if the server was added with one, with the time of its first and its last call. It is a random string made without sign-up.
Minerals’ own log stores no IP address. The host, Vercel, sees the address of each request to serve it and to limit abuse. Code, file contents and repo names are not stored.
A pull goes through a Minerals address that records it and redirects to the supplier. The file comes from the supplier. More on the about page.