Using Coppermind from claude.ai

How to use Coppermind directly in your browser via claude.ai, with zero local installation.

Who This Is For#

If you have a Claude Teams plan and want to use Coppermind without installing anything on your computer, the claude.ai connector is your path. It connects Coppermind to your browser-based Claude sessions so you can switch clients, store memories, search, and check brand voice -- all from claude.ai.

This is also the way to use Coppermind on a device where you cannot install software (a work laptop with restrictions, an iPad, a shared machine).

Setup (5 Minutes)#

1. Go to claude.ai and sign in with your Teams account
2. Open Settings (gear icon) then Connectors
3. Click + then Add Custom Connector
4. Fill in:

• Name: Coppermind CMO
• URL: https://api.coppermind.app/mcp
• Auth: Bearer token -- paste your Coppermind API key (starts with cm_)

1. Click Save

Once saved, Coppermind tools appear in all your claude.ai conversations. You do not need to repeat this setup.

What You Can Do#

The remote connector gives you the core CMO loop -- enough for daily check-ins, quick captures, and client context searches.

Switch Between Clients#

"Switch to Acme Corp"

Just like the desktop version, you switch between client minds to work in the right context.

Store and Search Memories#

"Remember that Acme wants to pause LinkedIn ads through Q2"

"What do we know about Acme's Q2 plans?"

Storing and searching works the same as the full version. Memories are shared across all access methods -- something stored from claude.ai is immediately searchable from Claude Code or Claude Desktop.

Quick Notes#

"Quick note: Josh mentioned they're hiring a new CMO at Bluebell"

Fast captures without needing to specify a memory type. Coppermind classifies it automatically.

Check and Set Brand Voice#

"What's Acme's brand voice?"

"Set Acme's brand voice to professional and concise with a focus on data-driven results"

View Recent Memories#

"Show me the latest memories for Acme"

This pulls up recent entries so you can review what Coppermind knows without running a full search.

Configure Client Settings#

"Set Acme's meeting cadence to weekly on Tuesdays"

Adjust per-client settings like meeting cadence, timezone, and EOS configuration if the client uses EOS.

Check Connection Health#

"Run a health check"

Verifies the connector is working and your database is reachable.

What You Cannot Do (Yet)#

The remote connector currently exposes 10 core tools. Some features require the full local MCP server:

The remote tool set will expand over time. For now, think of the claude.ai connector as your "quick access" path and the local install as the full-featured powerhouse.

Typical Workflows#

Before a Meeting (2 Minutes)#

"Switch to Acme Corp"
"What are the recent memories about Acme?"
"What's their brand voice?"

Skim the results to refresh your context before walking into a call. Not as rich as a full meeting prep brief, but enough for a quick refresher.

After a Meeting (1 Minute)#

"Switch to Acme"
"Quick note: Sarah approved the Q3 budget at $45K/month"
"Remember: We agreed to deliver the content calendar by Friday"
"Remember: They want to explore TikTok advertising in Q3"

Drop in the key takeaways before you forget. The full extraction pipeline will process the meeting transcript later if you use Claude Code.

Between Meetings#

"Search for everything about Bluebell's brand guidelines"
"What commitments are outstanding for Acme?"

Quick lookups to answer a question or prep for a call without opening a full desktop session.

How It Works Behind the Scenes#

The claude.ai connector talks to the same Coppermind gateway (api.coppermind.app) that the local MCP server uses. Your data is stored in the same database. Memories stored from claude.ai appear in Claude Code and Claude Desktop, and vice versa.

The connector uses your API key for authentication and the same rate limits apply as the REST API. Sessions last up to 24 hours before requiring a fresh connection (this happens automatically -- you will not notice it).

Troubleshooting#

"Couldn't reach the MCP server"#

Check that the URL is exactly https://api.coppermind.app/mcp (not just https://api.coppermind.app). The /mcp path is required.

"Authentication failed"#

Your API key may be expired or incorrectly pasted. Go to Settings, edit the Coppermind connector, and re-paste the key. Make sure there are no extra spaces.

Tools appear but return errors#

Run a health check. If the database is temporarily unavailable, try again in a few minutes. If the error persists, contact support.

"No client selected"#

Most tools require an active client. Run switch_client first:

"Switch to Acme Corp"

Should You Also Install Locally?#

If you only need to store notes, search memories, and check brand voice, the claude.ai connector is enough. Many CMOs start here and never need more.

If you want meeting prep briefs, automatic transcript ingestion, document synthesis, bulk knowledge import, team management, or EOS integration, install the local MCP server via the Claude Code plugin or the shell installer.

Both work together. There is no conflict between using the claude.ai connector and a local install -- they share the same data.

Organize With Claude Projects#

If you use Claude Projects (available on Teams and Pro plans), create one project per client and add auto-switch instructions. This gives you automatic client switching and clean mental separation. See Using Claude Projects with Coppermind for the full setup.

Related Guides#

• Using Claude Projects with Coppermind -- automatic client switching via Projects
• Installation and Setup -- full local install for Claude Code and Claude Desktop
• Plugin Installation -- one-command install for Claude Code users
• Memory Storage and Search -- how memories work
• Client Management -- managing client minds