BOTOPS
Menu
Book a demo

AI-agent first

Your delivery agent should be able to do the work—not just describe it.

Botops exposes a remote, authenticated MCP server with the tools and tenant data an AI agent needs to operate client bots while preserving human oversight.

One agency-scoped operating surface

READ

Understand the workspace

Inspect clients, bots, integrations, users, conversations, and transcripts with safe defaults.

ACT

Complete operations

Create and update clients, bots, credentials, users, widgets, and lifecycle state.

SYNC

Bring back outcomes

Reconcile Retell and Vapi calls and chats through bounded, retrying, idempotent jobs.

Designed for MCP clients

  • Remote Streamable HTTP JSON-RPC endpoint
  • Dedicated bearer token per agency, separate from ingest and provider keys
  • Declared read-only and mutating tool annotations
  • Structured tool results plus a workspace summary resource
  • Server-side demo immutability and tenant enforcement on every call

Humans keep the final view

The portal remains the place where agency teams and clients review bots, transcripts, access, branding, and agent-driven changes. MCP makes the system operable; the portal makes it accountable.

Questions

Frequently asked

Which AI agents can connect?

Any MCP client that supports remote HTTP and bearer authentication can use the Botops endpoint.

Does the MCP return private provider keys?

No. Private management keys are encrypted and never returned. Integration listings reveal only provider, label, and whether a browser key is configured.

Can the public demo MCP write?

No. Demo resources can be inspected with a demo credential, but every mutating tool is rejected before a database or provider write.

AI agent operations with MCP · Botops