Skip to content

Connect Claude or ChatGPT

Connect Claude, ChatGPT or another AI app to your Bookline account with the MCP address and your portal login.

You can connect an AI app to Bookline, ask it about your calls, agents, venues, campaigns and metrics, and have it make some changes for you. There is no key to paste into the app: you give it an address, log in with your portal account and choose the key it works with.

The app works with one of your API keys. Keys are managed in the portal, under Administration → API keys in the menu; the entry appears only if your account can read at least one customer. If you have no key yet, you can create one while connecting.

  1. In the app, add a custom connector or MCP server with this address:

    https://api.bookline.ai/mcp
    • Claude (web, desktop and mobile): under Settings → Connectors, add a custom connector.
    • ChatGPT: create a custom connector (you need a plan that allows them).
    • Other MCP apps: add a remote MCP server with the same address. Apps that follow the MCP authorization spec work.
  2. The app opens the Bookline page Connect an app to Bookline. Log in with your portal account if you are not logged in yet.

  3. Check which app is connecting and where connecting sends you back (see Verified apps).

  4. Choose the key the app will work with, or create a new one right there.

  5. Click Connect. You are back in the app and can start asking.

The page shows whether Bookline has verified the app:

  • Claude and ChatGPT appear by name, marked Verified.
  • Any other app appears as the web address connecting sends you back to, marked Not verified and with a warning. Anyone can give an app any name: trust the address, not the name. If you do not recognise it, cancel.

The app can do exactly what the key you choose can do, nothing more: the same scopes and the same venues.

  • You can only choose one of your own personal keys. An account key or someone else’s key will not work.
  • An app connected with a Bookline team key can read, but never change data.

The app sees these tools, each one a route of the API. It only gets answers for the ones its key has the scope for.

Domain Read Change
Metrics export_metrics
Venues list_venues, get_venue update_venue
Calls list_calls, get_call
Agents list_agents, get_agent update_agent (rename)
Knowledge bases list_knowledge_bases, get_knowledge_base create_knowledge_base, update_knowledge_base, delete_knowledge_base
Campaigns list_campaigns, get_campaign, list_campaign_runs, get_campaign_run pause_campaign
Phone numbers list_numbers, get_number
Integrations list_integrations, get_integration
Billing list_invoices, get_invoice, list_billing_services

The tools that change data follow the same rules as the API’s writes: the app reads the resource first and sends the version it read, so a change decided on an outdated read is refused and the app is told to read again. A create carries a request id, so a retry never creates twice. Writes need a key with the matching :write scope, which expires within 90 days. An app cannot remove a value (such as a venue’s website): do that through the API or in the portal.

The apps you connected appear in the portal under Administration → API keys, section Connected apps, with the key each one works with.

  • To remove an app’s access, click Disconnect.
  • Disconnecting the app, revoking its key or the key expiring ends the connection within about a minute.
  • A connection unused for 30 days expires. The app then asks you to log in again.

If your MCP app lets you add custom headers, you can also connect it to the same address by sending your key in the apikey header, as with the rest of the API (see Keys and scopes). The app then does not appear under Connected apps: to remove its access, revoke the key.