OpenClaw (MCP)

    Developer Guide

    Step-by-step: personal token, LUMENBASE_AGENT_TOKEN env, edit openclaw.json, restart gateway, verify CRM tools.

    By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20265 min read

    Ways to interact with Lumenbase

    OpenClaw

    AI agents

    Remote MCP

    Generate a token in Lumenbase, set LUMENBASE_AGENT_TOKEN where the gateway runs, add lumenbase under mcp.servers in ~/.openclaw/openclaw.json, restart, and use CRM tools from your agents.

    Open settings
    Good for
    OpenClaw agent setups
    Sign in
    Personal API token

    What this is

    Connect Lumenbase to your OpenClaw gateway as an MCP server. The gateway calls our hosted remote endpoint (streamable HTTP) with your personal token. You get the same CRM tool surface as Claude Connectors.

    You generate a token in Lumenbase, put it in an environment variable on the machine that runs the gateway, register the server in ~/.openclaw/openclaw.json, and restart. After that, CRM tools show under Agents → Tools.

    How to use Lumenbase in OpenClaw

    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. 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. 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. 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. 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. 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, then 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

    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.

    Prefer OAuth in Claude instead of managing a token file? See Claude (Connectors).

    What OpenClaw can do

    After setup, your agents can call 22 CRM tools in your workspace. They respect the same data-access rules as Lumo and Claude.

    Look up

    crm:read

    Search and summarize your workspace without changing data.

    ContactsCompaniesDealsTasksInvoicesActivitiesLinkedIn message historyRevenue at riskDaily briefingOutreach queue status

    Create

    crm:write

    Add new records and notes when you ask Claude to.

    ContactCompanyDealTaskInvoiceList membershipActivity noteRevenue at risk

    Update

    crm:write

    Change fields on existing records.

    ContactCompanyDealInvoiceRevenue at risk

    Remove

    crm:write

    Only when you explicitly ask. Claude flags these as destructive.

    Delete revenue at risk

    Outreach

    crm:write

    Send email or LinkedIn messages when you ask (remote queue requires extension session).

    Send emailSend LinkedIn messageQueue remote LinkedIn DM

    Advanced: local stdio (optional)

    If you prefer a child process on your machine instead of HTTPS, add a stdio server that runs the @lumenbase/mcp package. Put your token in the server env block (not the remote Bearer header + env interpolation pattern used for streamable HTTP).

    ~/.openclaw/openclaw.json (stdio fragment)
    {
  "mcp": {
    "servers": {
      "lumenbase": {
        "command": "npx",
        "args": ["-y", "@lumenbase/mcp@latest"],
        "env": {
          "LUMENBASE_AGENT_TOKEN": "<paste-your-token>",
          "LUMENBASE_API_URL": "https://api.lumenbase.io/functions/v1/openclaw-api"
        }
      }
    }
  }
}

    Generate the token on the Token tab, then run openclaw gateway restart. The Cursor tab in settings has the same stdio shape for copy-paste.

    If tools do not appear

    OpenClaw often fails MCP connections without an error in chat. The agent answers from training data instead. Check Agents → Tools, then the gateway log:

    Terminal
    openclaw logs --follow
    • Run openclaw gateway restart after adding or changing mcp.servers
    • Confirm LUMENBASE_AGENT_TOKEN is set in the gateway process environment (not only your shell)
    • Wrong transport: use streamable-http for lumenbase.io/api/mcp
    • Compare openclaw mcp show lumenbase with the URL and headers in the setup section above

    See also: Claude (Connectors) · REST API

    All four ways to interact with Lumenbase

    Was this article helpful?