Connect an AI Client

Estimated time: 5–10 minutes

Goal: connect one client, call mem_status, and confirm it uses the same database as the CLI.

Before You Connect

Complete Quick Start, then run:

mm status

Keep the displayed database path. You will compare it with the client result.

Manual MCP-only entries use the memtomem-server command. memtomem and mm are terminal CLIs and must not be used as MCP server commands. Official plugins may supply their own pinned launch command.

Pick one client below. If that client already has both a plugin and a manual MCP entry, use its matching rule instead of assuming that one copy is always removed:

Client	How entries are matched	Result
Claude Code	exact command and arguments	the same signature runs one server; a different signature runs both
Codex CLI	server name	manual memtomem wins; a different name runs both
OpenCode	mcp key	manual mcp.memtomem wins; a different key runs both

Claude Code

The official plugin is the recommended path. The current marketplace plugin is version 0.3.3 and bundles Core 0.3.12:

/plugin marketplace add memtomem/memtomem
/plugin install memtomem@memtomem
/reload-plugins

If /reload-plugins is unavailable, start a new Claude Code session. Then run:

/memtomem:status
/memtomem:remember Remember this confirmed decision: release smoke tests run before cutover.
/memtomem:search release smoke tests

The status should show the same database path as mm status, and search should return the saved sentence with a source path.

If you previously registered a manual server, run /mcp before continuing. Claude Code 2.1.218 matches the exact command and arguments; environment variables are not compared. The plugin signature is:

uvx --from memtomem==0.3.12 memtomem-server

With that same signature, the manual registration wins and only one server runs under mcp__memtomem__mem_*. The bare memtomem-server entries below have a different signature, so both servers run and tools appear under both mcp__memtomem__mem_* and mcp__plugin_memtomem_memtomem__mem_*.

/memtomem:setup reports this doubled namespace and shows the available remedies, but it never removes a registration automatically. Choose the setup you want:

• Keep the plugin (recommended): remove the manual entry with claude mcp remove memtomem. Add -s user when removing a user-scope entry; remove the project entry from .mcp.json.

• Keep only the manual server: run /plugin uninstall memtomem@memtomem.

• Keep the plugin commands with the manual server: keep the plugin installed and register the manual entry with the exact plugin signature. For example:

  claude mcp add memtomem -- uvx --from memtomem==0.3.12 memtomem-server

For MCP-only setup without the plugin’s commands and skills, choose one Claude Code registration scope:

Scope	Command	Visibility
Local	claude mcp add memtomem -- memtomem-server	current project and user
User	claude mcp add memtomem -s user -- memtomem-server	every project for this user
Project	commit a project-root .mcp.json	teammates after trust approval

{
  "mcpServers": {
    "memtomem": {
      "command": "memtomem-server",
      "args": []
    }
  }
}

Codex CLI

Install the official plugin:

codex plugin marketplace add memtomem/memtomem
codex plugin add memtomem@memtomem

Start a new Codex thread, then ask:

Use $memtomem-status to show the current memory database path.
Use $memtomem-remember to save this confirmed decision: release smoke tests run before cutover.
Use $memtomem-search to find "release smoke tests" and show the source.

For MCP-only setup, add this to ~/.codex/config.toml:

[mcp_servers.memtomem]
command = "memtomem-server"
args = []
supports_parallel_tool_calls = true

Restart Codex after changing the file.

Codex resolves MCP servers by name. If the plugin is also installed, the manual [mcp_servers.memtomem] section wins and only one server runs. Remove that section to switch to the plugin’s pinned server. Do not rename the manual section to [mcp_servers.memtomem-local]: a different name is not deduplicated, so both servers run. Confirm the resolved entry with codex mcp list.

JSON-Based MCP Clients

Use this server entry unless a client-specific section below says otherwise:

{
  "mcpServers": {
    "memtomem": {
      "command": "memtomem-server",
      "args": []
    }
  }
}

Client	Configuration location	After editing
Cursor	~/.cursor/mcp.json	restart Cursor
Windsurf	~/.codeium/windsurf/mcp_config.json	restart Windsurf
Claude Desktop on macOS	~/Library/Application Support/Claude/claude_desktop_config.json	quit and reopen the app
Claude Desktop on Windows	%APPDATA%\Claude\claude_desktop_config.json	quit and reopen the app
Gemini CLI	~/.gemini/settings.json	restart the CLI; new setups should prefer Antigravity CLI
Kimi CLI	~/.kimi/mcp.json, or $KIMI_SHARE_DIR/mcp.json	restart Kimi CLI

Kimi CLI can also be configured by the setup wizard:

mm init --mcp kimi

OpenCode

The published plugin provides an exact-pinned MCP server plus commands and skills. Add it to opencode.json:

{
  "plugin": ["opencode-memtomem@0.1.2"]
}

For MCP tools only:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "memtomem": {
      "type": "local",
      "command": ["uvx", "--isolated", "--from", "memtomem[all]==0.3.12", "memtomem-server"],
      "enabled": true,
      "timeout": 60000,
      "environment": {"MEMTOMEM_TOOL_MODE": "core"}
    }
  }
}

OpenCode applies the same-name rule to the mcp key. An existing mcp.memtomem entry wins over the plugin’s default and only one server runs. Remove that entry to use the plugin server. A differently named key such as mcp."memtomem-local" is not deduplicated, so both servers run.

Antigravity

Antigravity IDE and Antigravity CLI (agy) use separate files.

• IDE built-in Gemini agent: ~/.gemini/antigravity/mcp_config.json, with the generic mcpServers entry above.
• IDE VS Code-side integrations: ~/Library/Application Support/Antigravity/User/mcp.json, using that integration’s servers schema.
• Antigravity CLI: ~/.gemini/antigravity-cli/mcp_config.json:

{
  "mcpServers": {
    "memtomem": {
      "type": "stdio",
      "command": "memtomem-server",
      "args": []
    }
  }
}

Restart the agent session after editing. Antigravity does not inherit MCP entries from a separate VS Code installation.

Verify the Connection

Ask the client:

Call mem_status and show the database path, embedding provider, and chunk count.

The setup is complete when:

• exactly one memtomem server or tool namespace is active;
• the client exposes the nine default Core tools or the plugin’s guided workflows;
• mem_status succeeds;
• its database path matches mm status;
• a saved memory can be found with its source path in a new session.

mem_status and a matching database path can succeed even when two servers are active. Use /mcp in Claude Code, codex mcp list in Codex, or the exact mcp.memtomem key in OpenCode to verify the first condition.

If It Does Not Work

1. Run mm status to separate an installation problem from a client problem.
2. For a manual MCP-only entry, confirm the configured command is memtomem-server; an official plugin may use its own pinned command.
3. Apply the Claude Code, Codex, or OpenCode matching rule above and leave exactly one active server.
4. Restart the client or open a new session after plugin installation.
5. If a GUI-launched client cannot resolve a manual command, run command -v memtomem-server and use that absolute executable path in its configuration.
6. Continue with Troubleshooting if the database path or namespace differs.

Installing a client plugin does not index the project, import built-in memory, watch files, or save entire conversations. Use Index and Import Existing Content for those explicit operations.

Next

• Memory Across Sessions
• Index and Import Existing Content
• LTM MCP Tools
• LTM Operations & API