Connect Claude or Cursor to Your CRM via MCP
Connect Claude over OAuth or Cursor over Streamable HTTP to Lumenbase's remote MCP server. Read and update CRM records with your own account permissions.
You already work in Claude or Cursor. MCP lets those tools use your CRM from the same conversation. Lumenbase exposes one remote MCP server at `https://lumenbase.io/api/mcp`.
The client acts as your Lumenbase account. Record visibility, workspace permissions, OAuth scopes and Lumo capability controls still apply. Connecting an AI tool does not grant access to another person's private records.
Connect Claude with OAuth
In Claude, add Lumenbase as a custom connector using `https://lumenbase.io/api/mcp`, then approve access on Lumenbase. Team or Enterprise administrators may need to add the connector before members can connect.
You can also find the current app instructions in Settings > Personal > My integrations > Connect an AI app, under Connect by app. The Claude and ChatGPT guide covers permissions, app requirements and troubleshooting.
No local package or personal API token is needed for the OAuth connector. Inspect or disconnect individual clients in Connected clients on the same Lumenbase settings page.
Connect Cursor with a personal token
Open Settings > Personal > My integrations > MCP > Token and generate a personal token. Configure Cursor's MCP client to use Streamable HTTP at `https://lumenbase.io/api/mcp` with `Authorization: Bearer <your-token>`.
Use an environment variable for the token. Never commit the token to a shared configuration file. The MCP client guide contains the current Cursor configuration and token diagnostics.
The old stdio instructions relied on an unpublished package. Use the supported remote connection instead.
What the client can do
Depending on your access and granted scopes, the client can look up records, create or update deals, add tasks, log notes and read Feed recommendations. Inspect requested changes before approving them in the client.
An OAuth client can be read-only. A manual personal token provides read and write access as your account, so protect it and revoke it when no longer needed.
Troubleshoot a connection
For an OAuth authorization failure, reconnect the affected client and check its permissions. For Cursor, confirm the token reaches the client process as a Bearer header and has not been revoked. Tokens stop working when the user loses workspace membership.
Provider plan and administrator requirements can change. Use the current app instructions linked above rather than an old screenshot or package installation command.
Frequently asked questions
Can I connect Claude to Lumenbase?
Yes. Add `https://lumenbase.io/api/mcp` as a custom connector in Claude and approve OAuth on Lumenbase. Organization administrators may need to enable it first.
Does it work with Cursor too?
Yes. Use Streamable HTTP with the same remote URL and a personal token sent as a Bearer header. The supported setup does not require a local stdio package.
What is the MCP server URL?
`https://lumenbase.io/api/mcp`.
Where can I revoke access?
Disconnect OAuth clients in Settings > Personal > My integrations > Connect an AI app. Revoke manual tokens in Settings > Personal > My integrations > MCP > Token.
Was this article helpful?