Teleflows MCP server: user guide
The Teleflows MCP server lets AI assistants such as Claude and ChatGPT read your Teleflows data and answer questions about it in plain language. It is read-only: nothing in Teleflows can be created, changed or deleted through it.
Server address: https://mcp.teleflows.io
Reads Teleflows at: api.teleflows.io
Reads Teleflows at: api.teleflows.io
1. Create an API key
- In Teleflows at api.teleflows.io, open Settings → API keys and create a key. Keys from another Teleflows environment are not accepted.
- Name it after the app, for example Claude. A separate key for each app lets you revoke one without affecting the others.
- Choose a role (see the next section) and an expiry, up to one year.
- Copy the key. You can only see the full key once.
More about keys, roles and expiry: Teleflows API documentation.
2. Choose the key's role
The assistant sees exactly what the key's role can see. Only roles whose permissions fit within your own are available.
- Pick the role that can read the data you want to ask about: calls, campaigns, routing, reports.
- A smaller role means the assistant sees less. Some questions are then answered with fewer records, an empty list, or "not allowed for your role".
- Read-only use never needs a role that can change data; this server cannot change anything in any case.
3. Connect your app
Claude (claude.ai and the Claude apps)
- Open Settings → Connectors and choose Add custom connector.
- Enter a name, such as Teleflows, and the server address. Select Add, then Connect.
- Sign in on the Teleflows page that opens (next section).
On Team and Enterprise plans, an organization owner adds the connector first; each member then connects with their own key.
ChatGPT
- Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode (paid plans).
- Add a new app or connector with a name and the server address, and choose OAuth as the authentication.
- Sign in on the Teleflows page that opens (next section).
Claude Code
- Run this in a terminal:
claude mcp add --transport http teleflows https://mcp.teleflows.io - Run
/mcpin Claude Code, choose teleflows and sign in.
Other MCP apps
Add the server address as a remote (HTTP) MCP server. Sign-in opens in your browser.
4. Sign in safely
Before you paste your key, check the sign-in page:
- It names the app you are connecting and the address you will be sent back to, for example claude.ai or chatgpt.com.
- An app marked unverified chose its own name. Continue only if you started the connection yourself and recognise the address.
Where your key is kept. The key is stored encrypted on
the Teleflows MCP server and used only to read data for you. The assistant never sees it. A
connection lasts up to 90 days; after that, you sign in again.
5. What you can ask
| Area | For example |
|---|---|
| Calls | "Show my last 10 calls" · "How many calls yesterday, by campaign?" · "Is there a recording for this call?" |
| Campaigns | "List my active campaigns" · "Which publishers send traffic to campaign X?" · "Which tracking numbers belong to campaign X?" |
| Routing | "Which buyers are active?" · "Show the routing plan for campaign X" · "What are the caps and recent pings for ring tree target X?" |
| Setup | Workflows, variables, audio files, blocked numbers, pixels, postback and predictive configs |
| Monitoring | "Show this week's conversion receipts" · "Where is target X used?" |
6. Good to know
- Read-only. Requests to change something are refused.
- Dates. Up to 31 days per question; ask for longer periods in parts. Times are in UTC.
- Counts and totals come from Teleflows' own call reports. Very long lists are returned in pages.
- Data is shown as Teleflows returns it. Where Teleflows does not document what a value means, the assistant says so instead of guessing.
7. Disconnect or revoke access
- Remove or disconnect the connector in your app's settings.
- To stop all access at once, revoke the key in Teleflows (Settings → API keys). Expired and revoked keys cannot make requests, so every connection that uses the key stops working.
8. Troubleshooting
| You see | Why | What to do |
|---|---|---|
| Claude says "wasn't connected" right after signing in | The page shows an earlier status; the sign-in itself completed | Reload the page; the connector is usually already connected. |
| "Teleflows did not accept this key" | The key is incomplete, expired or revoked | Copy the whole key again, or create a new one. |
| "Too many attempts for this sign-in" | Several wrong keys in one sign-in | Start the connection again from your app. |
| "Not allowed for your role" | The key's role cannot read that data | Use a key with a role that can, or ask a Teleflows admin. |
| An empty answer | No records in that period, or the role cannot see them | Try another period, or check with a key that has more access. |
| The assistant stops working after some weeks | The key expired or the connection reached 90 days | Connect again; create a new key if it expired. |