Cursor and Other MCP Clients

If your client can launch an MCP server, the default Coppermind path is the local runtime-backed MCP server:

{
  "mcpServers": {
    "coppermind": {
      "command": "coppermind",
      "args": ["mcp", "serve"]
    }
  }
}

Recommended setup

npm install -g coppermind
coppermind setup
coppermind daemon start
coppermind doctor

Then add the MCP config above to your client.

Expected tools

Once the client reloads the MCP config, you should see:

• memory_search
• memory_ingest
• memory_get
• memory_stats
• memory_delete

Why this is the default path

This route keeps the normal product story simple:

• local-first
• no account required
• no API key required
• no manual database setup required

If you are using Cursor specifically

Use the same local MCP config unless you intentionally want the advanced direct-cloud MCP path.

If it does not work

Start with:

coppermind doctor
coppermind daemon health

Then make sure the client actually reloaded the MCP config.

Advanced cloud path

If you explicitly want the direct cloud-connected package instead of the local runtime-backed server, see Published Cloud MCP (Advanced).