Connect Cursor

Connect Cursor

This tutorial walks through adding memory as a stdio MCP server in Cursor so Composer and agent features can recall durable memories.

Prerequisites

• Cursor installed and signed in.
• A Linux or macOS machine with shell access.
• The ability to add MCP servers in Cursor settings.

1. Install the binary

Run the installer:

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 ~/.local/bin is on the PATH Cursor sees, or use the full binary path in step 2.

2. Generate the MCP config snippet

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

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 also includes those environment variables.

Example output:

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

The command prints the snippet to stdout — it does not write Cursor’s config automatically.

3. Add the server in Cursor

Open Settings → MCP and add a new stdio server using the values from the generated snippet:

Field	Value
Name	memory
Command	Use the command value from the snippet
Arguments	Use the args array values (e.g., --db /home/yourname/.memory/default.db)

Alternatively, if your Cursor version supports importing JSON directly, paste the mcpServers object.

If you prefer to configure manually without running the setup command, use absolute paths for both the binary and the --db flag.

4. Start a fresh chat

Cursor discovers tools when a chat starts. Open a new Composer or agent chat so the memory tools are loaded.

5. Verify the connection

Ask Cursor to check health:

Call memory_health.

You should see a JSON health report. If it fails, re-run the install:

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

Then check that the command path in the MCP settings is absolute and that the parent directory for the database exists.

6. Test recall

Ask Cursor to remember a preference:

Remember that I keep frontend components under 200 lines.

Then start a new chat and ask:

What do you know about my component size preferences?

Cursor should recall the fact from the local store.

Expected output

• od3sa-memory version prints a version string.
• memory_health returns status: ok.
• A remembered preference is returned when asked in a new chat.

Troubleshooting

• Server exits — ensure --db uses an absolute path and the parent directory exists.
• Command not found — add ~/.local/bin to your PATH, or use the absolute binary path.
• Config not picked up — start a new Cursor chat after changing the MCP config.
• Stale Python wrapper from an old install — if od3sa-memory fails with ModuleNotFoundError: No module named 'memory_memory', remove the broken wrapper and reinstall:

  rm -f ~/.local/bin/od3sa-memory
  curl -fsSL https://0d3sa.com/memory/install.sh | sh

Next steps

• Connect another MCP client
• Sync two devices with a relay
• Tools reference
• Skills registry