Claude (Connectors)

    Setup Guide

    Paste the MCP URL in Claude Connectors, sign in on Lumenbase, and see what CRM tools Claude can use.

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

    Ways to interact with Lumenbase

    Claude

    AI agents

    Custom connector · MCP

    Add Lumenbase as a custom connector in Claude, then use CRM tools in chat. This uses the production remote MCP endpoint with workspace-scoped access.

    Open settings
    Good for
    Claude.ai, Claude Desktop, Cowork (directory connector)
    Sign in
    OAuth (Connectors); stdio uses personal token

    What this is

    Connect Lumenbase inside Claude as a custom connector. You paste one URL in Claude, sign in on Lumenbase when prompted, and Claude can use your CRM tools in chat. Same data as the app and OpenClaw, scoped to your workspace.

    This guide is for Claude on the web and Claude Desktop when they support remote MCP + OAuth. For a local MCP file on your computer, see the advanced section at the bottom.

    How to use Lumenbase in Claude

    Add Lumenbase as a custom connector in Claude, sign in once on Lumenbase, then use CRM tools from chat.

    1. Open Customize

      In Claude, open Customize. You will see Skills, Connectors, and plugins in the sidebar.

      Open Claude Connectors
      • Open Customize from the Claude sidebar or menu
      • You should see Skills, Connectors, and Connect your apps

    2. Click Connectors

      Open Connectors from Customize. Before adding Lumenbase, your custom connector list should be empty.

      • Open Connectors and verify the list is empty before adding Lumenbase
      • Then click + to add your custom connector

    3. Click +, then Add custom connector

      In Connectors, click + and choose “… Add custom connector” from the menu.

      • Click + in Connectors, then choose “… Add custom connector”
      • The Add custom connector dialog opens next

    4. Give the name and put the Remote MCP server URL

      In the Add custom connector dialog, set the name to Lumenbase and paste the Remote MCP server URL, then click Add.

      MCP server URL (paste in Claude)

      https://lumenbase.io/api/mcp

      Leave OAuth Client ID and Client secret empty in Claude — registration is automatic. Only fill them if your admin gave you Anthropic-held credentials (claude-connector plus a secret).

      • Name: Lumenbase
      • Remote MCP server URL: https://lumenbase.io/api/mcp, then click Add

    5. It will look like this when connected

      On the new Lumenbase connector row, click Connect or Authorize and allow access on Lumenbase. After approval, Claude shows Lumenbase as connected with URL and tool permissions.

      • After approval, the connector appears under Web as connected
      • You should see URL + tool permissions and a Disconnect button
      Consent URL (only from Claude): lumenbase.io/oauth/claude

    6. Start a chat and make a CRM request

      Return to Claude, start a chat, and ask for a CRM action within Lumenbase capabilities, like creating or listing records.

      • Start a chat and make a CRM request in plain language
      • Approve the prompt when Claude asks to use Lumenbase tools

    How auth works

    Where auth happens: after you save the connector in Claude, use Connect or Authorize on that connector. Claude sends you to lumenbase.io/oauth/claude to sign in and approve. Lumenbase returns an OAuth token to Claude. You never paste a CRM password into Claude.

    crm:read: List and fetch CRM records, activity timelines (including LinkedIn messages), Daily briefing, and outreach queue status.
    crm:write: Create, update, delete (where allowed), and send email or LinkedIn messages on your behalf.

    Revoke anytime: Settings → My Integrations → OpenClaw, then delete the row labeled Claude connector.

    If the consent page does not load, refresh and try Connect in Claude again. You can also use a personal token and local MCP (advanced) from the OpenClaw integration tab.

    What Claude can do

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

    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 MCP (stdio)

    For Claude Desktop or Cursor with a local MCP process, generate a personal token under Settings → My Integrations → OpenClaw and follow the Claude Desktop (stdio) card there. That path does not use Connectors or OAuth.

    Prefer the remote connector above when Claude supports it. No API token stored in a file on disk.

    Events

    CRM changes from connector tools can emit outbound events (Zapier, webhooks) when enabled for your workspace. Configure under Settings → Integrations. See Zapier setup.

    See also: OpenClaw (MCP) · All interfaces

    All four ways to interact with Lumenbase

    Was this article helpful?