Start free trial
Docs sections

API and MCP

Connect an AI assistant

Add Botlum to claude.ai, ChatGPT, Claude Code or Codex by its URL and sign in: no keys to copy.

How it works

You give your assistant one URL. It finds out from Botlum how to sign in and opens a Botlum page in your browser. There you sign in as usual, choose the workspace, and allow read access. You do not create or copy a key. The assistant then reads that workspace on your behalf.

The URL is:

https://dash.botlum.com/mcp

claude.ai and Claude Desktop

  1. Open the settings, go to Connectors, and choose Add custom connector.
  2. Name it "Botlum" and paste the URL above.
  3. Click Connect. A Botlum page opens: sign in, pick the workspace, click Allow.
  4. In a chat, turn the Botlum connector on in the tools menu and ask, for example: "How visible were we in AI answers last month?"

On team plans of Claude, an owner may need to add the connector for the organization first.

ChatGPT

  1. Open Settings, then Apps & Connectors. Custom connectors may need developer mode, under the advanced settings.
  2. Create a connector, paste the URL above, and choose OAuth as the authentication.
  3. Sign in to Botlum in the window that opens, pick the workspace, and allow access.
  4. Choose the connector in a chat and ask your question.

Claude Code

claude mcp add --transport http botlum https://dash.botlum.com/mcp

Then run /mcp in Claude Code, choose botlum and authenticate. Your browser opens the Botlum sign-in page.

Codex

codex mcp add botlum --url https://dash.botlum.com/mcp
codex mcp login botlum

The login command opens the Botlum sign-in page in your browser.

One URL per workspace

With https://dash.botlum.com/mcp you choose the workspace on the sign-in page. To fix the workspace in the URL instead, put its name from the app's address before /mcp: 

https://dash.botlum.com/your-workspace/mcp

This is handy for agencies: add one connector per client workspace, and each one can only ever read its own client. A token from another workspace is refused on that URL.

Seeing and disconnecting assistants

In the app, open API and MCP in the workspace. Connected apps lists the assistants you connected, with when they were connected and last used. Disconnect signs one out at once. An assistant also loses access as soon as you leave the workspace.

Why an assistant asks you to sign in again

A connection stays signed in for 30 days of disuse and renews itself while you use it. You are asked to sign in again after a long pause, after you disconnect the assistant, or if you lost access to the workspace.