# Install Minerals
What this is: Minerals is the marketplace for agents. One connection, and every request is routed to the right library or tool. It is contact hello@minerals.dev.
What this guide does: adds one MCP server for all projects, and pulls nothing without a yes.
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, this guide's first run). No code, files or repo name.
Keep your reply short. Say what you did.
1. Add the server for all projects, with the command for your client. If a server named minerals already exists, leave it and go on.
   - Claude Code: `claude mcp add --scope user --transport http minerals https://minerals.dev/mcp`
   - Cursor: add `"minerals": { "url": "https://minerals.dev/mcp" }` under `mcpServers` in `~/.cursor/mcp.json`; merge this into the existing file; keep every other server
   - Codex: `codex mcp add minerals --url https://minerals.dev/mcp`
   Then reply with this one line, for every project, and say nothing else in this reply: "Minerals is connected. Restart <client> once, then tell me what you are building."
   The first run stops there: it does not label the project, fetch find.md or suggest anything.
If your person carries on without restarting, the steps for that are at https://minerals.dev/guide.md.
