Every serious CRM was built decades ago and never fully rebuilt.

Lumenbase is a new CRM for the AI age that helps you prioritize your day and engage with the right people in your network.

Full-funnel CRM with lists, leads, deals, and accounts; Lumo AI for daily priorities and outreach; automations, lead scoring, forecasting, and integrations with Gmail, Outlook, Slack, LinkedIn, and more.

Try for free · Features · How it works · AI site digest

    Lumenbase

    Connect Claude or Cursor to Your CRM via MCP

    Setup Guide

    Lumenbase exposes a remote MCP server at lumenbase.io/api/mcp. Connect Claude over OAuth, or Cursor over stdio, and run your CRM from your AI tools.

    By Sebastian StreiffertPublished Jun 2, 2026Updated Jun 2, 20266 min read

    You already work in Claude or Cursor. Your CRM sits in another tab. MCP closes that gap. Lumenbase runs an MCP server, so your AI tool can read and update the CRM directly.

    MCP stands for Model Context Protocol. It's the standard that lets an AI host talk to outside systems. Lumenbase supports both the remote and local flavors.

    Connecting Claude (Connectors)

    Claude uses the remote MCP server. The setup:

    After that, Claude can pull contacts, deals, and tasks, and make changes, from inside a normal chat.

    1. Open Settings, then Integrations, then Openclaw, then the Claude tab.
    2. Add the remote MCP URL: `https://lumenbase.io/api/mcp`.
    3. Approve the OAuth consent screen at `/oauth/claude`.

    Connecting Cursor (stdio MCP)

    Cursor uses the local stdio MCP setup instead of the remote URL. You'll find it under Settings, then Integrations, then Openclaw, then the Cursor tab. The package is documented as `packages/lumenbase-mcp`.

    So the same CRM works from your editor and your chat tool.

    What you can do once connected

    With Claude or Cursor wired in, you can:

    You type the request in plain language. The AI calls the CRM and reports back.

    • Look up a contact or company by name
    • Create and update deals
    • Add tasks and log activity notes
    • Pull a Today briefing through the agent tools

    Auth, in short

    Remote MCP uses Bearer tokens through OAuth (`mcp-oauth`). The Claude consent flow lives at `/oauth/claude`. If you hit repeated auth errors, reconnect under Settings rather than fiddling with parameters.

    Who this is for

    Revenue operators at $2M to $30M ARR companies who'd rather run the CRM from the tools they already use. People comfortable in Claude or Cursor who don't want to context-switch to update a deal.

    Frequently asked questions

    Can I connect Claude to Lumenbase?

    Yeah. Add the remote MCP URL `https://lumenbase.io/api/mcp` under Settings, Integrations, Openclaw, Claude tab, then approve OAuth.

    Does it work with Cursor too?

    Yes. Cursor uses the stdio MCP setup on the Cursor tab, documented in the `lumenbase-mcp` package.

    What's the MCP server URL?

    `https://lumenbase.io/api/mcp`.

    I keep getting auth errors. What now?

    Reconnect the integration under Settings, Connections. That clears most repeated auth failures.

    Was this article helpful?