Browse docs

MCP

Tap to expand

Contribute

MCPUpdated 2026-03-18

Claude Desktop Setup

Connect RetainDB MCP to Claude Desktop with the current package entrypoint, current environment variables, and the modern primary tool verbs.

Use this path when you want Claude Desktop to call RetainDB tools directly against your projects and local workspace.

What you need

  • Claude Desktop installed
  • Node.js available on the same machine
  • a RetainDB API key starting with rdb_
  • an optional default project slug

The basic config

Add a RetainDB server entry to your Claude Desktop MCP config:

json
{
  "mcpServers": {
    "retaindb-context": {
      "command": "npx",
      "args": ["-y", "@retaindb/mcp-server@latest"],
      "env": {
        "RETAINDB_API_KEY": "rdb_...",
        "RETAINDB_API_URL": "https://api.retaindb.com",
        "RETAINDB_PROJECT": "my-project"
      }
    }
  }
}

What matters here:

  • command launches npx
  • args resolve the current MCP package
  • RETAINDB_API_KEY authenticates tool calls
  • RETAINDB_PROJECT gives Claude a default project when the tool call does not specify one

Setup flow

  1. add the server block to Claude Desktop's MCP config
  2. save the file
  3. restart Claude Desktop completely
  4. ask Claude to call a simple RetainDB tool

A good first smoke test

Start with low-risk primary verbs:

  • search
  • search_code
  • remember

If Claude can retrieve context, search code, or store one remembered fact, the MCP bridge is working.

Common mistakes

Wrong environment variable name

Use RETAINDB_API_URL if you need a non-default base URL.

Old tool names from stale examples

Prefer modern primary verbs like search, search_code, and remember. Older legacy-style tool names in stale screenshots or copied configs are out of date.

Forgetting the restart

Claude Desktop generally needs a full restart after config changes.

Expecting automatic project selection

If RETAINDB_PROJECT is missing, some tools may still work, but the initial experience is smoother when a default project is set.

When setup fails

Check these in order:

  1. npx can run on the machine
  2. the rdb_* API key is valid
  3. the project slug, if set, actually exists
  4. Claude Desktop was fully restarted
  5. the requested tool name is part of the current MCP surface

Next step

Once Claude Desktop can start the server, continue to semantic search tools or security and scope controls. If you still need the broader tool overview, read setup tools.

Was this page helpful?

Your feedback helps us prioritize docs improvements weekly.