
minerals
dev.minerals/minerals
The marketplace for agents. It routes each design request to the right library or tool.
Documentation
Minerals
One connection. Every request is routed to the right library or tool.
Website · Connect · How it works · List your work · Changelog
What it is
Minerals is one MCP server for design work. Connect it once to Claude Code, Cursor or Codex. When your agent is about to choose, install or write a UI component, a texture, an animation or another design element, it asks Minerals, and Minerals routes the request to a library or tool made for exactly that.
- Curated. Every listing is added and judged by hand.
- Light. At most three results, best first. One offer per session. Nothing is added without your yes.
- Pass-through. Files come straight from their makers. Minerals never holds them.
- Open. One connection, no sign-in.
Connect
The quick way: paste this to your agent.
Connect Minerals for all my projects: read https://minerals.dev/install.md and follow it.
Or add the server yourself:
Claude Code
claude mcp add --scope user --transport http minerals https://minerals.dev/mcp
Cursor
Or add this to ~/.cursor/mcp.json:
{ "mcpServers": { "minerals": { "url": "https://minerals.dev/mcp" } } }
Codex
codex mcp add minerals --url https://minerals.dev/mcp
Also a plugin, a skill and a shadcn item
# Claude Code plugin
/plugin marketplace add Mineralsdev/minerals
/plugin install minerals@minerals
# Agent skill
npx skills add Mineralsdev/minerals
# shadcn
npx shadcn@latest add Mineralsdev/minerals/connect
How it works
- Your agent asks. It sends a few keywords when the work calls for it. Never code or files.
- The request is routed. It goes to the listings that fit the task. At most three come back, best first.
- You say yes. The agent asks once, in one line.
- The file comes from its maker. Minerals never holds it.
- Then it stays out of the way. At most one offer per session, and "Not now" is remembered.
On the shelf
| Listing | Maker | Best for |
|---|---|---|
| Jesper Vos | A carousel that keeps the browser's own scrolling and adds dragging with a mouse. Layout, snapping and spacing stay in your CSS. | |
| Details.so | Page transitions, parallax, small interface details. | |
| Josh Puckett | Tuning spacing, motion and colour live beside the interface. | |
| Micka | Refined product interfaces with one consistent hover feel across buttons, tables, dialogs and sidebars. | |
| Jakub Antalik | Effects for AI interfaces in React: a glowing border while it streams, thinking orbs while it works, and voice and avatar pieces. | |
| Jesper Landberg | Sticky elements that ease into place and out again instead of stopping dead. One file, no dependencies. | |
| Textures.dev | Animated, hover-reactive brand textures for websites. Each one is a single React component that coding agents like Claude Code, Cursor and Codex add to your project with one prompt. | |
| Materic, Inc. | Sharing a prototype or an agent's design explorations with other people to compare, review and give feedback on a shared canvas. | |
| Elia Kuratli | Animated components and blocks for marketing pages on shadcn and Next.js. |
The live shelf, with every item, is at minerals.dev.
The tools
| Tool | What it does |
|---|---|
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. |
A search takes up to three needs, separated by commas. get_listing takes up to eight refs, separated by commas. A report is only for a pull that was not used after all: a pull that went through needs none.
After a pull your agent says one line, the receipt: "Added
The command
An item that is pulled as a registry file comes with one command:
npx -y minerals@1 add arc/hero-section
It reads the item's record from minerals.dev, downloads the file from its supplier, checks it against the hash Minerals recorded, installs it, and records the pull under installed in minerals.json. It never replaces a file that exists unless it is run with --overwrite, and it stops when a file has changed since it was checked unless it is run with --allow-changed. Its source is in cli/.
What is sent, what is fetched
What is sent: a few keywords, any filter you set (section, listing, kind, free only), stack names, one project type and stage label, the moment the work is at, the refs and settings already in minerals.json (what is installed, what was accepted or declined, and quiet), whether your person asked to replace something, your client's name, the install key when the connect line carries one, and which path asked (for example, the install guide's first run). No code, files or repo name.
Nothing is pulled without a yes. On a yes, the file comes straight from its supplier. Minerals never holds it. A pull goes through a Minerals address that records it and redirects to the supplier. More in the privacy policy.
For makers
Made something an agent should reach for? Listing is free, and every listing is added and judged by hand. Send it in.
Licence
The files in this repo are under the MIT licence. Each listing keeps its own licence, named on its page. Contact: hello@minerals.dev
No installation packages available.
