Skip to content
0d3sa

Connect another MCP client

Connect another MCP client

Section titled “Connect another MCP client”

memory speaks the Model Context Protocol (MCP) over stdio. This tutorial shows the generic server config for any MCP-compatible client, plus a quick verification.

Prerequisites

Section titled “Prerequisites”
  • A Linux or macOS machine with shell access.
  • An MCP client that supports stdio servers.
  • The ability to edit the client’s mcpServers JSON or server list.

1. Install the binary

Section titled “1. Install the binary”

Run the installer:

Terminal window
curl -fsSL https://0d3sa.com/memory/install.sh | sh

This downloads the right binary for your platform, verifies its checksum, and installs it to ~/.local/bin/od3sa-memory. Make sure the directory is on the PATH your client sees, or use the absolute binary path in the server config.

2. Generate a config snippet

Section titled “2. Generate a config snippet”

The setup command can print a paste-ready JSON snippet with absolute paths for your system:

Terminal window
od3sa-memory setup --print-mcp-json

This prints an mcpServers JSON block with the resolved binary path and database path. If you have set MEMORY_ORG_ID or MEMORY_WORKSPACE_ID, or run setup claude in a project directory for Claude identity wiring, the snippet includes those in the env block as well. The command prints to stdout — it does not write any files.

3. Add the server config

Section titled “3. Add the server config”

Use the generated snippet, or construct the config manually. The server command is:

Terminal window
od3sa-memory --db /home/yourname/.memory/default.db

Use your real username. The --db path must be absolute, and the parent directory must exist.

If your client uses a mcpServers JSON config, paste the output from setup --print-mcp-json, or add this manually:

{
  "mcpServers": {
    "memory": {
      "command": "/home/yourname/.local/bin/od3sa-memory",
      "args": [
        "--db",
        "/home/yourname/.memory/default.db"
      ],
      "env": {
        "MEMORY_LOG_LEVEL": "INFO"
      }
    }
  }
}

Replace /home/yourname with your actual home path. If od3sa-memory is on the client’s PATH, you can use the bare command name.

4. Restart your client

Section titled “4. Restart your client”

MCP servers are usually loaded when the client starts. Restart or reload the client after adding the server.

5. Verify the connection

Section titled “5. Verify the connection”

Ask your agent to run memory_health. You should see a JSON health report. If it fails:

  1. Re-run the install:
    Terminal window
    curl -fsSL https://0d3sa.com/memory/install.sh | sh
  2. Confirm the --db path is absolute.
  3. Confirm the parent directory for the database exists.
  4. Check that the binary path in the server config is correct for the client’s environment.

6. Test remember and recall

Section titled “6. Test remember and recall”

Ask your agent to store a fact:

Remember that I use Python for examples and keep sentences short.

Then start a new conversation and ask:

What do you know about my writing preferences?

The agent should recall the fact from the local store.

Expected output

Section titled “Expected output”
  • od3sa-memory version prints a version string.
  • memory_health returns status: ok.
  • A stored fact is returned when asked in a new session.

Tool names

Section titled “Tool names”

The exact tool names depend on your client’s MCP prefix. Common patterns are:

  • memory_remember
  • memory_recall
  • memory_search
  • memory_search_semantic
  • memory_edit
  • memory_forget
  • memory_forget_expired
  • memory_health
  • memory_vacuum

See the tools reference for full schemas.

Next steps

Section titled “Next steps”