Connect Lumenbase to your OpenClaw gateway as a remote MCP server: get a token in Lumenbase, expose it to the gateway, edit ~/.openclaw/openclaw.json, restart, and use CRM tools from your agents.

1. 1

   Generate a personal API token

   In Lumenbase, open Settings → My Integrations → OpenClaw → Token. Click Generate token, copy the value once, and store it somewhere safe — you cannot view it again.

   Open Token settings →

   • Open Settings → My Integrations → OpenClaw → Token
   • Copy the token immediately — Lumenbase will not show the full value again
2. 2

   Put the token where the gateway can read it

   Set the environment variable LUMENBASE_AGENT_TOKEN in the same environment that runs openclaw gateway. Your openclaw.json references it as ${LUMENBASE_AGENT_TOKEN} in the Authorization header — do not paste the raw secret into the JSON file when using this pattern.

   Environment variable (LUMENBASE_AGENT_TOKEN)

   export LUMENBASE_AGENT_TOKEN="<paste-your-token>"

   Set this where openclaw gateway runs, not only in your interactive shell, if the gateway is a background service.

   • Variable name: LUMENBASE_AGENT_TOKEN
   • The gateway process must inherit this variable — not only your login shell
3. 3

   Edit openclaw.json (mcp.servers)

   On the gateway machine, edit ~/.openclaw/openclaw.json. Under mcp.servers, add a lumenbase entry with the remote MCP URL, streamable-http transport, and Bearer header. Use a url entry — not command/args (those start a local stdio child process).

   ~/.openclaw/openclaw.json (mcp.servers fragment)

   {
     "mcp": {
       "servers": {
         "lumenbase": {
           "url": "https://lumenbase.io/api/mcp",
           "transport": "streamable-http",
           "headers": {
             "Authorization": "Bearer ${LUMENBASE_AGENT_TOKEN}"
           }
         }
       }
     }
   }

   CLI alternative (then restart)

   openclaw mcp set lumenbase '{"url":"https://lumenbase.io/api/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${LUMENBASE_AGENT_TOKEN}"}}'
   openclaw gateway restart

   Remote MCP URL: https://lumenbase.io/api/mcp · transport streamable-http

   • File: ~/.openclaw/openclaw.json under mcp.servers
   • Use url + streamable-http — not command/args for this remote server
4. 4

   Restart the gateway

   Save openclaw.json (or finish openclaw mcp set), then restart the gateway so MCP servers reload.

   • Run openclaw gateway restart after any MCP change
   • openclaw mcp list should include lumenbase
5. 5

   Confirm CRM tools in OpenClaw

   In the OpenClaw dashboard, open Agents → Tools. Lumenbase tools should be listed (MCP tools are separate from skills). Start a chat and ask for a CRM action; approve tool use when prompted.

   • Dashboard: Agents → Tools — confirm Lumenbase CRM tools appear
   • If chat ignores CRM data, run openclaw logs --follow

   Do not paste your token into openclaw.json when using $${LUMENBASE_AGENT_TOKEN} in the Authorization header — set the environment variable instead.

How auth works: the gateway sends your personal token as Authorization: Bearer … to https://lumenbase.io/api/mcp. Tools run as you in your workspace — same data-access rules as Lumen and Claude Connectors. Claude uses OAuth instead of a file/env token.

Generate or revoke tokens: Settings → My Integrations → OpenClaw → Token. Do not commit tokens to git or paste them in chat.