OpenClaw

What you get

Connect OpenClaw to Graphory and your agent's working memory survives restarts and gains typed relationships. Research, decisions, and cross-session context flow into the same graph every other AI client in your stack can read and write.

Graphory-specific setup

These are the pieces Graphory controls. Drop them into OpenClaw's MCP servers config using the format OpenClaw currently documents.

• MCP URL: https://api.graphory.io/mcp
• Auth header: Authorization: Bearer gs_ak_YOUR_KEY
• Get your key: app.graphory.io/settings/api-keys

Example config block, for reference. OpenClaw's exact key names evolve, so treat this as one possible shape and check the vendor docs below for the current syntax:

{
  "mcpServers": {
    "graphory": {
      "url": "https://api.graphory.io/mcp",
      "headers": {
        "Authorization": "Bearer gs_ak_YOUR_KEY"
      }
    }
  }
}

Once connected, OpenClaw can call Graphory's MCP tools to search the graph, pull timelines, and write new findings back. That same memory is visible from Claude Desktop, Claude Code, Cursor, and any other MCP client you wire up.

Vendor setup docs

OpenClaw's MCP configuration flow, config file locations, and supported transport fields change with each release. We deliberately do not mirror OpenClaw's docs here, because they drift. For the current, authoritative setup steps, go straight to the source: