DocsClients

Choose Your Client

Choose the right local-first setup path for Codex, Claude Code, Cursor, Hermes, or another MCP-capable client.

integrationproviderscodexclaude-codehermescursor

Coppermind supports several client shapes, but the starting question is simple:

Which client are you trying to connect today?

Fast recommendations

If you use...Start hereWhy
CodexCodex SetupManaged local MCP install, with optional hooks later
Claude CodeClaude Code SetupManaged local MCP install
Cursor or another MCP clientCursor and Other MCP ClientsGeneric local MCP config
HermesHermes SetupRuntime-managed patcher path

Codex

Choose Codex if you want:

  • a managed local MCP install
  • explicit memory tools
  • optional automatic capture later through hooks

Go to Codex Setup.

Claude Code

Choose Claude Code if you want:

  • a managed local MCP install
  • the local-first path without cloud setup

Go to Claude Code Setup.

Cursor and other MCP clients

Choose this path if your client can launch an MCP server but does not have a dedicated Coppermind installer.

Go to Cursor and Other MCP Clients.

Hermes

Choose Hermes if you want memory woven into the session lifecycle instead of exposed mainly as explicit tools.

Go to Hermes Setup.

Advanced cloud path

If you explicitly want the direct cloud-connected MCP package instead of the local runtime-backed path, that lives here:

That is a secondary path, not the default onboarding story.

If you want the shortest route

The shortest common path is still:

  1. Quick Start
  2. pick your client guide
  3. run coppermind doctor if anything looks wrong