Skip to main content

BESS AI in Claude

Manage your call center by talking to Claude. The BESS AI connector puts the platform inside Claude: build and publish agents, test them over chat, place real phone calls, run outbound campaigns, create website widgets, and read your analytics — all from a conversation.

Connector URL:

https://mcp.bess-ai.com/mcp

Works on any paid Claude plan. No API key needed.

  1. In claude.ai, open Settings → Connectors and click Add custom connector.
  2. Paste https://mcp.bess-ai.com/mcp and confirm.
  3. Click Connect. Your browser opens the BESS AI sign-in (if you are not already signed in) and then the authorization screen.
  4. Review the access being granted and click Allow access.

:::note Which account gets connected? The connection binds to whoever is signed in at platform.bess-ai.com in that browser — your Claude account email and your BESS account email do not need to match. Access is granted to your active organization (shown on the authorization screen), and only organization admins can approve. Teammates in the same organization can each connect their own Claude account; every connection is separate and individually revocable. :::

  1. Back in claude.ai, open a chat and make sure the BESS AI tools are enabled (the tools menu near the message box). Try: "What's my BESS credit balance?"

Connect from Claude Code or Claude Desktop​

These surfaces can also authenticate with an API key instead of OAuth. Create a scoped key under Settings → API Keys (leave out the API-keys permissions; you can also set a daily call cap), then:

claude mcp add --transport http bessai https://mcp.bess-ai.com/mcp \
  --header "Authorization: Bearer bess_sk_YOUR_KEY"

In Claude Desktop, add a custom connector with the same URL and header.

What Claude can do​

GroupTools
DiscoveryPlatform orientation and documentation search
AgentsCreate, list, inspect, update, and publish agents
CallsStart a real phone call or a web test call; read call details and history
ChatRun text conversations with your agents — including test mode for drafts
CampaignsCreate outbound batch campaigns; check status; start/pause/resume/cancel
WidgetsCreate and manage embeddable website widgets, get the embed code
AccountCredit balance, call analytics, your phone numbers

A typical flow: describe the agent you want → Claude creates it → test it together over chat and refine the prompt → publish → attach it to a call, a campaign, or a widget.

Safety and control​

  • Confirmation before spending. Tools that ring a real phone or spend credits (single calls, campaigns, campaign start/resume) are marked destructive — Claude always asks you before running them.
  • Scoped access. A connection can use agents, calls, chat, campaigns, widgets, and read-only analytics/billing/phone-number data. It can not manage API keys, change billing, or touch account settings.
  • Daily call cap. Every Claude connection gets its own access credential with a 200 calls/day cap by default. Find it under Settings → API Keys (named "Claude connector — …") to raise, lower, or remove the cap. When the cap is hit, call-starting tools return a clear error until the next UTC day.
  • Disconnect anytime. Remove the connector in claude.ai settings. Reconnecting later issues a fresh credential.

Troubleshooting​

  • "Authorization request expired" on the consent screen — the request is valid for 10 minutes. Start the connection from Claude again.
  • "Admin access required" — only organization admins can approve a connection. Ask an admin, or switch your active organization to one you administer.
  • Daily call cap reached (429) — the connection hit its per-day call limit. An admin can raise it under Settings → API Keys, or wait for the UTC day to roll over.
  • Claude says the connection needs re-authentication — sessions refresh automatically in the background; you are only asked again if the connection was revoked or unused for over 30 days. Reconnecting takes two clicks.

Learn more​