Connect

Add Minerals to your agent once. After that it works in two ways.

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/mcp

Cursor

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/mcp

Any other client

A remote MCP server over Streamable HTTP, with no sign-in:

https://minerals.dev/mcp

Making 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/mcp

Other ways

Add to Cursor

Claude Code plugin

claude plugin marketplace add Mineralsdev/minerals claude plugin install minerals@minerals

Skills

npx skills add Mineralsdev/minerals

shadcn

npx shadcn@latest add Mineralsdev/minerals/connect

The five MCP tools

What your agent can call. find_design is the front door; the other four follow from its answers.

What is logged

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.