Which Package Should I Install?

Most users should install coppermind.

Coppermind is the product you install. MCP is one of the main ways you connect a client to it. That means the normal day-one path is:

1. install coppermind
2. run it locally
3. connect your client through MCP or a runtime-managed integration

The short answer

What most users should do

Install:

npm install -g coppermind

Then follow Quick Start.

That gets you:

• the local runtime
• coppermind mcp serve
• managed installers for supported clients
• coppermind doctor as the repair path

When the SDK makes sense

Use @coppermind/sdk when you are building your own application or worker and you want to call Coppermind's managed cloud routes directly from code.

This is an app-developer path, not the normal local install story.

When the published cloud MCP package makes sense

Use @coppermind/mcp only when you intentionally want the direct cloud-connected MCP route instead of the local runtime-backed MCP path.

That is an advanced path. It requires:

• a Coppermind account
• a Coppermind API key
• comfort with a cloud-connected setup

If that is not what you want, use coppermind mcp serve through the normal coppermind install.

Managed installers vs published packages

These commands install the local-first client wiring:

coppermind mcp codex install
coppermind mcp claude install
coppermind mcp antigravity install

They are safe config writers. They do not install the third-party client binary itself.

If you are still unsure

Use this rule:

• if you want memory for yourself in a supported coding client, install coppermind
• if you are writing software that integrates with Coppermind's cloud APIs, use @coppermind/sdk
• if you explicitly want a cloud-only MCP setup, use @coppermind/mcp

Then continue with Choose Your Client.