Skip to main content

AI - Artificial Intelligence - Voipstudio MCP Server

The Voipstudio MCP (Model Context Protocol) server gives AI assistants such as Claude and ChatGPT direct, secure access to your Voipstudio account data, including recordings, CDRs, live calls, voicemails and the history of your conversations with a number. Once connected, the assistant can query calls, analyse patterns, surface agent performance issues and generate QA reports in plain English, with no custom development required.

Add the CX Addon and each recording arrives pre-enriched with a transcript, summary, sentiment, action items and a CX score. This greatly reduces the work the AI has to do, which keeps token use down and costs more predictable.

MCP server URL​

This is a remote MCP server (Streamable HTTP transport). You connect it by signing in with your Voipstudio account: there is no API key to create or paste.

How connecting works​

When you add the server to an AI application, the application opens a Voipstudio sign-in page:

  1. Sign in with your Voipstudio email and password, and your 2FA code if two-factor authentication is on, or with Google, Microsoft or Apple if your account uses single sign-on. The account must already exist: a new account cannot be created from this page.
  2. A consent page shows who is asking for access. It names the address that will receive access, and the application when it is a known one (Claude, ChatGPT) or runs on your own computer. Any other website is shown with a warning: allow it only if you recognise the address.
  3. Click Allow to connect, or Cancel to connect nothing.

The assistant can then see what your Voipstudio user can see, and nothing more.

The API key each application gets​

When you click Allow, the server creates a Voipstudio API key for that application in your user's API Keys section. Its name starts with VoIPstudio MCP - followed by the application, for example VoIPstudio MCP - Claude (claude.ai) [1a2b3c4d].

  • Each connected application has its own key. Signing in again from the same application replaces only that application's key, so your other applications stay connected.
  • A user can hold up to 10 of these keys. Connecting an eleventh application removes the one used least recently.
  • A key expires after 30 days without use. Normal use, including the application renewing its sign-in in the background, keeps it active.
  • To disconnect an application, remove the connector in the application, or delete its key in API Keys. After the key is deleted, the application's tool calls report that the connection was removed, and the application asks you to sign in again.

Connecting to Claude​

In Claude (web or desktop app), add Voipstudio as a custom connector:

  1. Open Settings → Connectors and choose Add custom connector. On Team and Enterprise plans, an owner adds the connector for the organisation.
  2. Enter a name, for example Voipstudio, and the MCP server URL above.
  3. Click Connect and complete the sign-in and consent steps described above.

Claude can now use the Voipstudio tools in any conversation. The first time a tool is called, Claude asks you to confirm. Choose Always allow to skip this prompt in future.

Claude Code​

claude mcp add --transport http voipstudio https://mcp.voipstudio.com/mcp
claude mcp login voipstudio

Your browser opens the sign-in page. After Allow, click Continue to hand the sign-in back to Claude Code.

On a machine without a browser, for example over SSH, run claude mcp login voipstudio --no-browser instead. Open the address it prints in a browser on any computer, sign in and allow access, then copy the address the final page shows and paste it into Claude Code when prompted.

Connecting to other AI platforms​

Any AI application that supports remote MCP servers with sign-in (OAuth) can connect using the URL above, for example ChatGPT, where your plan allows custom connectors. Look for an option labelled custom connector, custom MCP or remote MCP in the application's settings, enter the URL, and complete the sign-in and consent steps. The exact menus depend on the application and your plan.

Applications that can only send a fixed API key cannot connect: this server accepts only the sign-in it issues itself.

For developers​

The server implements MCP authorization:

  • OAuth 2.1 authorization code flow with PKCE (S256) and dynamic client registration. Metadata is published at https://mcp.voipstudio.com/.well-known/oauth-authorization-server and https://mcp.voipstudio.com/.well-known/oauth-protected-resource/mcp.
  • Access tokens are valid for one hour and are renewed with a refresh token. A refresh token stays valid while it is used at least once every 30 days.
  • Only initialize and tools/list work without a token. A Voipstudio API key is not accepted as a bearer token.
  • Requests are limited per client address: client registration 20 an hour, token requests 50 and authorization requests 100 per 15 minutes.

To call the server through the Claude API's MCP connector, your application obtains an access token through the flow above and passes it as the server's authorization_token. See Anthropic's MCP connector documentation for the request format.

CX Addon​

Without the CX Addon, recordings arrive as raw metadata. The AI must transcribe and analyse each call itself, consuming significant tokens per recording.

With the CX Addon, Voipstudio handles transcription, summarisation, sentiment analysis, action extraction and CX scoring on its own infrastructure at a fixed monthly cost with no per-call fees and no transcription limits. The AI receives finished intelligence, ready to reason over immediately.

Without CX AddonWith CX Addon
TranscriptThe AI must fetch audio and transcribe/translate✓ Included, speaker-diarised
SummaryThe AI must generate✓ Included
SentimentThe AI must infer✓ Included
Action itemsThe AI must extract✓ Included
CX scoreNot available✓ 1–10 on every call
Approx. tokens/call10,000–15,000300–500
Cost modelVariable AI spendFixed monthly subscription

Fields unlocked by CX Addon​

FieldTypeDescription
transcriptstringFull word-level transcript
transcript_speakersobjectSpeaker-diarised transcript segments
summarystringConcise summary of the call outcome
sentimentstringCustomer sentiment: positive, neutral, negative
cx_scorenumber (1–10)Customer experience score
metadata.timelinearrayKey moments and action items extracted from the call

Tools Reference​

With MCP you do not need to learn the Voipstudio API: you ask in plain language, and the AI chooses the tools and reads the data for you.

For technical users who want to know what happens "under the hood", the server provides the six tools below. All of them only read data.

get_recordings​

Returns call recordings. With the CX Addon active, each record includes the transcript, summary, sentiment, CX score and timeline. Without the addon, these fields are null.

Parameters

ParameterTypeDefaultDescription
filtersarray—Filter objects, see Filtering, sorting and pagination below
sortobject—{ "by": "<field>", "dir": "ASC" } or "DESC"
limitnumber10Records per page (1–1000)
pagenumber1Page number

Response fields

FieldTypeDescription
idnumberUnique recording ID
call_idnumberLinks to CDR call_id
timestampstringRecording start (UTC, YYYY-MM-DD HH:mm:ss)
callerstringCalling party number
calledstringCalled party number
src_namestringAgent name (source)
dst_namestringDestination name
durationnumberDuration in seconds
typestringI = inbound, O = outbound
contextstringCall context (e.g. LOCAL_USER, QUEUE)
transcriptstring | nullFull transcript (CX Addon)
transcript_speakersobject | nullDiarised transcript (CX Addon)
summarystring | nullCall summary (CX Addon)
sentimentstring | nullCustomer sentiment (CX Addon)
cx_scorenumber | nullCX score 1–10 (CX Addon)
metadata.timelinearray | nullKey events & actions (CX Addon)

Example – Low CX scores this week

Ask: "Show me all recordings from this week where the CX score was below 6, grouped by agent, with a summary of what went wrong on each call."

The AI calls the tool with:

{
"filters": [
{ "property": "timestamp", "operator": "gte", "value": "2026-11-09 00:00:00" },
{ "property": "cx_score", "operator": "lt", "value": 6 }
],
"sort": { "by": "cx_score", "dir": "ASC" },
"limit": 100
}

get_cdrs​

Call Detail Records – the raw log of every call leg. Use for volume stats, cost analysis, duration distributions and agent activity summaries. Available without the CX Addon.

Parameters: same as get_recordings (filters, sort, limit, page)

Key response fields

FieldTypeDescription
call_idnumberUnique call identifier
calldatestringCall start timestamp (UTC)
src_namestringAgent / caller name
dst_namestringDestination name
billsecnumberBillable seconds
durationnumberTotal seconds including ringing
dispositionstringCONNECTED, NO ANSWER, BUSY, FAILED
chargenumberCall cost
typestringI = inbound, O = outbound
src_uastringSource device / softphone user-agent
labelsarrayCustom tags applied in Voipstudio

get_live_calls​

Returns a real-time snapshot of all active calls on your account. No parameters required.

Example: "How many calls are in progress right now, and which agents are on them?"

get_voicemails​

Fetches voicemail messages. Same filters, sort, limit and page parameters as get_recordings.

Key fields: caller, callerid, dialled (the number that was dialled), origtime (when the message was left), duration, folder, is_new, transcript

get_recording_audio​

Returns the address of the MP3 audio of one recording, with its caller, called number, time and duration.

Parameter: id (number) — the id field from a get_recordings response.

info

The address is on the Voipstudio API. Downloading it needs a Voipstudio API key sent in the x-auth-token header, so the AI receives the address, not the audio.

get_history_for_number​

Lists the conversations, calls and SMS, with one phone number on your account.

Parameters

ParameterTypeDefaultDescription
numberstring—The phone number (required)
fromDateTimestring—Optional start, YYYY-MM-DD HH:mm:ss
toDateTimestring—Optional end, YYYY-MM-DD HH:mm:ss

Response fields (one entry per call or message): channel, date, direction (Inbound or Outbound), src, dst, src_name, dst_name, content

Example: "Show me every call and SMS with +44 20 7946 0000 this month."

Filtering, sorting and pagination​

get_recordings, get_cdrs and get_voicemails accept an optional filters array. Each filter object has three properties:

PropertyDescription
propertyAny field of the tool's response (e.g. calldate, cx_score, src_name)
operatoreq, ne, lt, lte, gt, gte, in, like, notlike (the symbols =, !=, <, <=, >, >= also work)
valueString, number, or array (for in operator)

The date field differs per tool: calldate for CDRs, timestamp for recordings, origtime for voicemails.

Results are sorted with sort, for example { "by": "calldate", "dir": "DESC" }, and paged with limit (default 10, at most 1000) and page (default 1).

Common examples​

Date range (CDRs)

[
{ "property": "calldate", "operator": "gte", "value": "2026-06-01 00:00:00" },
{ "property": "calldate", "operator": "lte", "value": "2026-06-30 23:59:59" }
]

CX score threshold (recordings)

[{ "property": "cx_score", "operator": "gte", "value": 8 }]

Specific agent

[{ "property": "src_name", "operator": "eq", "value": "Jane Ryder" }]

Connected calls only (CDRs)

[{ "property": "disposition", "operator": "eq", "value": "CONNECTED" }]

Inbound calls over 5 minutes (CDRs)

[
{ "property": "type", "operator": "eq", "value": "I" },
{ "property": "billsec", "operator": "gt", "value": 300 }
]

Use Cases​

Agent QA report​

"Give me a QA summary for each agent this month — CX score averages, common complaint themes, and their three lowest-scoring calls with summaries."

Call centre volume stats​

"What was our call volume by day this week? What was our average handle time, and how many calls went unanswered?"

Sentiment trend analysis​

"Is customer sentiment improving or declining compared to last month? Which call topics correlate with negative sentiment?"

Missed call follow-up list​

"List all missed inbound calls from the last 24 hours with caller IDs, so I can prioritise callbacks."

Customer history​

"Show me every call and SMS we have had with +44 20 7946 0000 this year, and summarise what was discussed."

Cost & billing review​

"Which extensions have made the most expensive outbound calls this quarter?"

Live operations check​

"How many agents are currently on calls, and are there any calls that have been running over 20 minutes?"

Token Efficiency​

Each call the AI analyses without the CX Addon requires it to process audio content and generate its own transcription and analysis. The CX Addon offloads this entirely to Voipstudio:

What Voipstudio handles (fixed monthly cost, unlimited calls):

  • Audio transcription
  • Speaker diarisation
  • Call summarisation
  • Sentiment classification
  • Action item extraction
  • CX scoring

What the AI receives: clean, structured text fields ready for reasoning, comparison and reporting.

This means you can ask the AI to analyse hundreds of calls in a single session at a fraction of the token cost, making large-scale QA, trend analysis and agent coaching reports practical without unpredictable AI spend.