OpenClaw Memory Integration

Pensyve gives OpenClaw agents persistent memory across sessions. Start with the MCP integration for explicit memory tools, then add the native plugin if you want relevant memories recalled before each turn and new context captured afterward.

Connect over MCP

Cloud

For interactive use, register the managed endpoint in explicit OAuth mode:

openclaw mcp add pensyve --url https://mcp.pensyve.com/mcp --transport streamable-http --auth oauth

Complete browser consent when OpenClaw prompts. No Pensyve API key is required for this MCP connection.

API-Key Fallback

For unattended automation, create a key at pensyve.com/settings/api-keys, export it in your shell, and add the managed MCP endpoint to openclaw.json:

export PENSYVE_API_KEY="psy_your_key_here"

{
  "mcpServers": {
    "pensyve": {
      "type": "http",
      "url": "https://mcp.pensyve.com/mcp",
      "headers": {
        "Authorization": "Bearer ${PENSYVE_API_KEY}"
      }
    }
  }
}

Local

Build the local MCP server:

git clone https://github.com/major7apps/pensyve
cd pensyve
cargo build --release -p pensyve-mcp

Then point OpenClaw at the binary:

{
  "mcpServers": {
    "pensyve": {
      "type": "stdio",
      "command": "/path/to/pensyve/target/release/pensyve-mcp",
      "args": ["--stdio"],
      "env": {
        "PENSYVE_NAMESPACE": "my-project"
      }
    }
  }
}

Both transports expose the same 10 memory tools. See the MCP tools reference for their parameters.

Add the Native Plugin

The optional native plugin adds automatic recall and capture hooks plus five OpenClaw-native tools. Build it from a Pensyve checkout:

cd integrations/openclaw-plugin
npm install
npm run build
openclaw plugins install --link "$PWD"
openclaw plugins doctor

Configure the plugin in openclaw.json:

{
  "plugins": {
    "entries": {
      "pensyve": {
        "enabled": true,
        "config": {
          "baseUrl": "https://mcp.pensyve.com",
          "entity": "my-agent",
          "autoRecall": true,
          "autoCapture": true,
          "recallLimit": 5
        }
      }
    },
    "slots": {
      "memory": "pensyve"
    }
  }
}

The native plugin's automatic hooks call Pensyve's REST API and do not reuse the MCP client's OAuth session. For cloud hooks, export PENSYVE_API_KEY before starting OpenClaw; the plugin reads it from the environment. The direct MCP connection above can continue to use browser OAuth. A local gateway does not require a key.

For a local gateway, set baseUrl to http://localhost:3000 and omit apiKey. Start that gateway with:

cargo run -p pensyve-mcp-gateway

What the Plugin Adds

The plugin stores memories under the configured entity, so use a stable value for each agent or project that should share context. The cloud gateway isolates data by authenticated tenant; the local stdio server uses PENSYVE_NAMESPACE for project-level isolation.

Verify the Integration

After restarting OpenClaw, ask it to store a distinctive project fact, start a new session, and recall that fact. For the native plugin, openclaw plugins doctor should report no plugin issues, and /pensyve stats should show the active connection and memory counts.

For more detail, see the maintained integrations/openclaw-plugin guide.