Skip to main content
The Bota MCP server exposes your project’s data as tools — list devices, inspect recordings, trigger test webhooks, and more — without leaving your IDE. It works for two audiences:
  • Developer tier — authenticated with your sk_live_* or sk_test_* key. Full project access.
  • End user tier — authenticated with an eut_* token you issue on behalf of a specific end user. Scoped to their recordings only.
MCP endpoint: https://api.bota.dev/mcp

Developer Setup

Connect with your existing API key. No new credentials needed.
Once connected, you can ask your assistant things like:
  • “List my devices and show me which ones haven’t synced in 24 hours”
  • “Get the transcription for recording rec_abc123”
  • “Trigger a test recording.uploaded event to my webhook”

Developer Tier Tools


End User Tokens

You can give an end user a scoped MCP token so they can query their own recordings with an AI assistant. The token is tied to a specific end_user_id and cannot access any other user’s data.

Issue a token

The token is shown only once. Copy the connection_command and send it to your end user. Issuing a new token automatically revokes any previous token for that end user.

Revoke a token

End User Tier Tools

Once connected with an eut_* token, the end user can query their own data: No admin operations. No access to other end users’ data.

Docs Search MCP

A separate Mintlify-hosted MCP server is available for searching Bota documentation:
This exposes search_bota — useful when you want an AI assistant to look up Bota API details on demand.