AgentRecall MCP Server

MCP server that gives your AI agents persistent memory. Works with Claude Code, Claude Desktop, Hermes Agent, OpenClaw, and any MCP-compatible client.

Quick Start

# Install
pip install agentrecall-mcp

# Run (cloud mode)
AGENTRECALL_API_KEY=ark_your_key agentrecall-mcp

Setup by Client

Claude Code

claude mcp add --transport stdio --scope user \
  --env AGENTRECALL_API_KEY=ark_YOUR_KEY_HERE \
  agentrecall -- agentrecall-mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "agentrecall": {
      "command": "agentrecall-mcp",
      "env": {
        "AGENTRECALL_API_KEY": "ark_YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop after saving.

OpenClaw

openclaw mcp set agentrecall '{"command":"agentrecall-mcp","env":{"AGENTRECALL_API_KEY":"ark_YOUR_KEY_HERE"}}'

Hermes Agent

Add to ~/.hermes/config.yaml:

mcp_servers:
  agentrecall:
    command: "agentrecall-mcp"
    env:
      AGENTRECALL_API_KEY: "ark_YOUR_KEY_HERE"

Then restart: hermes gateway restart

Any MCP Client

The server uses stdio transport. Point your MCP client to:

AGENTRECALL_API_KEY=ark_YOUR_KEY agentrecall-mcp

Configuration

How Agent-Specific Keys Work

API keys are bound to specific agents. When you create a key in the dashboard, you select which agent it belongs to. This means:

• No agent_id needed — The key remembers which agent it's for
• Better security — Each key only accesses one agent's memories
• Multiple keys — Create separate keys for different environments (dev, staging, prod)

Available Tools

License

MIT