Skip to main content

MCP

Beta

The MCP server is in preview (telebroad-reports v0.1.0). It is read-only and today exposes reporting data only. Details here — tools, scopes, endpoints — may change before general availability.

MCP (the Model Context Protocol) is an open standard that lets an AI assistant call external tools. Telebroad runs an MCP server so an assistant like Claude or ChatGPT can answer questions about your account's call activity — "how many calls did the sales queue miss last week?" — by querying your reporting data directly, in natural language, with no custom integration on your side.

It is read-only. The assistant can look at reporting data; it cannot change anything, send messages, or play call audio.

What you're connecting to, at a glance:

DetailValue
Endpointhttps://api.account.telebroad.com/mcp
TransportStreamable HTTP — a single POST carries all traffic
AuthOAuth 2.1 (for a person's assistant) or an API key (for a machine)
Scopereports:read — call history, KPIs and saved reports. No audio, no message content.
Servertelebroad-reports, MCP protocol 2025-06-18

What it exposes​

  • 10 tools — describe what your reports can answer, resolve names to IDs, summarise KPIs, break down AI call insights, list and fetch individual calls, read transcripts, search by what was said, and run your saved reports. See Tools & resources.
  • 2 resources — two short guides the assistant reads to interpret your data correctly (how the KPIs are defined, and which tool answers which question).

What it does not do​

  • No changes. It cannot create, edit or delete anything — it only reads.
  • No call audio. It can tell you a call was recorded, but never returns a recording URL. Use the recordings API for audio.
  • No messages or sending. It is reporting only — not SMS, not calling.
  • One account. A credential only ever sees its own account's data.

Who it's for​

  • A person connecting their assistant — you sign in on Telebroad's screen and your assistant gets a token scoped to what you can already see. Start with Connecting an AI client.
  • A machine or back-end — authenticate with an API key instead. Also covered in Connecting.

Before it works​

MCP is off by default for every account. You have to turn it on first — see Enabling MCP — otherwise every connection is refused.