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 a secret project key (sk_live_* / sk_test_*) or restricted key (rk_*). Hosted discovery lists only tools allowed by the credential’s scopes.
  • End user tier — authenticated with a Bota-issued eut_* token enrolled through Platform’s MCP Access feature or your trusted backend for a specific end user. Scoped to their own supported resources.
MCP endpoint: https://api.bota.dev/mcp

Developer Setup

Connect with your existing API key. No new credentials needed.
Restricted-key tool filtering and shared REST/MCP processing limits are a source preview pending the corresponding backend release. Browser OAuth for direct hosted MCP is planned; the current connection uses an API key.

Local stdio bridge to hosted MCP

Clients that launch a local stdio process can opt in to the hosted contract:
The public 0.2.0-beta.0 CLI cohort includes --mode hosted; its pinned source defines the client contract. Pin that exact version as shown in the CLI guide. Default bota mcp continues to use the existing 16 local compatibility tools. Package installation, a backend development deployment, or checks for one tool cohort do not establish complete migration, native-host acceptance or production support.
The hosted mode is a transport bridge for cloud tools. The selected API origin and configured credential determine the upstream service and role: project keys receive authorized developer tools, while eut_* credentials receive end-user tools. Your existing enrollment and token lifetime rules are unchanged; this mode adds no Platform login, browser authorization or OAuth flow. Restart the bridge after changing its selected credential or API origin. This CLI cohort also supports explicit environment profiles: bota --profile work mcp --mode hosted. These accept project developer keys only, verify the injected key’s project/organization before startup, and bind the API origin. They save no key and have no legacy credential fallback. Both local modes retain this startup context; local profile removal does not revoke the key or stop a running bridge. End-user-token compatibility without --profile remains separate from this developer profile cohort. The cohort also supports secure API-key profiles on qualified Windows hosts: bota --secure-profile work mcp --mode hosted. These reread profile state and verify identity for every list/call; removed or pending profiles stop later requests. They do not retain a startup bearer. Enrollment happens separately with hidden terminal input; MCP never prompts. Storage/runtime/permission refusal has no fallback. This is separate from environment-profile startup behavior and from Platform enrollment activation. For a qualified Platform deployment, enroll separately through ordinary CLI login before starting a developer-profile bridge. Optional --no-browser keeps the login command alive while its post-custody stderr URL opens in a browser on the same computer; default OS-browser launch remains available. MCP never starts consent itself. Installing this client does not activate the production enrollment service or establish a live login. For each tool-list request, the bridge obtains the currently authorized hosted inventory and forwards its schemas, descriptions, effect annotations, pagination cursor and continuation unchanged. Tool invocation similarly returns the hosted result, including structuredContent and isError, rather than rebuilding a local result. Existing sensitive output remains governed by the hosted tool’s scope checks and contract; the bridge adds no broader output redaction promise. This cohort implements tool listing and final tool results. It does not relay progress or inventory-change notifications, resources, prompts, tasks, sampling or elicitation. Those capabilities require separate server and client support. Hosted mode therefore has observable differences from the legacy local tools: The bridge keeps no tool-inventory cache and makes no automatic retry or legacy fallback. The hosted server authenticates and authorizes each request anew. Client applications may still retain a tool list: the current stateless backend does not reliably deliver tool-list-change notifications. Refresh discovery explicitly or restart the MCP connection after scope changes; calls remain subject to current admission even while an old client list is visible. Each bridge request has a total 30-second budget, with cancellation and shutdown closing local work and its upstream connection. A disconnected or cancelled request does not prove remote processing stopped or a mutation rolled back. Keep an uncertain outcome and reconcile resource or authorized delivery state before intentionally issuing another action. The bridge never automatically replays a mutation after disconnection. This opt-in mode does not change the default CLI tool set, public API SDK availability, or API publication boundaries. See CLI mode selection. 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

See operation scopes. get_project_identity needs a secret or restricted project key and no unrelated business scope. It returns credential facts, including an empty restricted scope list, without reading business resources. The hosted stdio bridge discovers it; the default legacy local set is unchanged. get_recording combines three reads and needs recording, transcription and summary read scopes. The existing list_webhooks result includes signing secrets, so it requires both webhooks:read and webhooks:write. Testing a webhook requires webhooks:write. Webhook tools do not expose Platform webhook management through public REST. Creating a transcription or summary starts processing and is subject to the same processing limits and input validation as REST. Reading a stored result does not start a new job. The CLI cohort includes the five integration-administration tools. Their availability and admission still require the matching deployed backend; client publication alone establishes neither. Hosted and local MCP share the bounded contract. In default legacy mode, the five local integration tools forward to hosted MCP, while older local tools retain their existing implementation and shapes. Legacy discovery lists all five integration tools, with hosted admission on every forwarded call. In opt-in hosted mode, discovery itself also comes from the authorized hosted inventory. Visibility never grants invocation rights, and this does not establish a completed default migration. Read tools require integrations:read, while test/update/delete require integrations:write. They return safe metadata and has_error instead of raw provider error text. No tool accepts or returns a raw provider key, and update_integration accepts only id and is_enabled. Enter or replace credentials in Platform or through CLI standard input outside the conversation. Stored-key tests check basic provider validity and applicable policy; they do not prove full processing or approve a provider route. See the REST, CLI and MCP support table. Credential tests are currently unavailable for HIPAA/GDPR projects because no credential-test route is approved; processing-route approval does not enable these checks.

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.