PBXfactory

Yeastar V25.1: AI Receptionist with MCP

Published August 18, 20264 min readby The PBXfactory team

Yeastar P-Series Cloud V25.1 (firmware 84.24.0.30) lets the AI Receptionist connect to MCP servers — one connection that gives it a whole set of tools and data — and send an SMS during a call. AI call transcription gets global rules and a feature code, and ring group members can send calls to voicemail.

Yeastar made P-Series V25.1 generally available for the Cloud Edition on 18 August 2026, as firmware 84.24.0.30, after a beta on 28 July. The GA build fixed poor audio on G.722 trunks and a mismatch in AI usage figures. The new features continue a clear direction: an AI Receptionist that doesn't just talk, but connects to the systems your business runs on. Here's what changed, from Yeastar's release notes.

What MCP is, in plain words

MCP — the Model Context Protocol — is an open standard for connecting AI assistants to tools and data. Instead of wiring up every action one by one, you connect the AI to an MCP server, and that server offers a set of tools: look up a customer, check stock, create a booking. Many software vendors now offer MCP servers for their products, and you can build your own.

Yeastar published an explainer, "What Is MCP? How It Connects AI Receptionists to Your Business", on its blog on 7 August, ahead of this release.

How the Yeastar AI Receptionist uses MCP

V25.1 adds:

  • MCP server support: add MCP servers to the PBX, giving the AI receptionist access to external tools and data through one connection.
  • An "MCP Server" skill: during a call, the receptionist can call tools on its assigned MCP server to look something up or take an action — the notes give checking an order and booking an appointment as examples.
  • Logging: each MCP tool call is written to the call records with the server name, tool name, status, request parameters and response.

V24.3 introduced custom tools — single HTTP requests you define yourself. MCP is the bigger version of the same idea: a bundle of tools, kept up to date by whoever runs the server.

Keep it safe

Connecting an AI to your systems is powerful, so the usual care applies. Give the MCP server only the access the receptionist needs, prefer read-only tools for a start, and check the call records to see what it actually did.

New skill: send an SMS during the call

The AI Receptionist can now send an SMS during a call through the PBX's SMS channel — an order confirmation, a code, appointment details. The caller hangs up with the information in writing. This needs an SMS channel set up on the PBX, which means an SMS-capable provider.

The Skill tab can also sort skills by default order or by whether they're switched on.

AI call transcription: rules and a feature code

  • Global transcription rules: transcribe calls automatically by type — internal, outbound or inbound. Only extensions allowed to use transcription are affected.
  • A feature code to start or pause transcription during a call, available once AI Call Transcription is switched on.

If you transcribe calls, the same care applies as with recording: tell people, and check the rules in your country.

Other changes in V25.1

  • Ring groups and queues: a global option lets members and agents who have voicemail send an incoming call to their voicemail from the call window.
  • Live Chat: channels get a standalone link, so you can share the chat in an email, not only embed it on a website.
  • SIP trunks: an RTP keep-alive option that sends comfort noise after 10 seconds of silence, and an option to send SIP requests to the registered IP.
  • Hot desking: an emergency outbound caller ID per phone, so emergency services receive the right location information.
  • Exports: choose what to export for extensions and the organisation.
  • Fixes: missing transcripts in voicemail emails, LDAP caller name lookups, and Zendesk pop-ups for merged contacts.
  • API: a new time zone interface, and AI tool-call details in the AI context returned for a call.

Where to start with MCP

If you're curious but not sure where to begin, start small. Pick one question callers ask all the time that needs live data — "where is my order?" is the classic — and connect one read-only tool for it. Watch the call records for a week. When it answers well, add the next tool.

What this means for you

On a Yeastar P-Series Cloud PBX from PBXfactory, Yeastar's updates are applied for you in announced maintenance windows, and urgent security fixes sooner.

The AI Receptionist runs on minutes; minutes beyond the included free ones are a paid Yeastar add-on — ask our support whether it's available for your PBX. We don't sell SIP trunks or SMS, so the SMS skill needs a channel from a provider of your choice. Connecting MCP servers is PBX configuration: Yeastar's documentation covers it, and our support packages can help.

Questions and answers

What is MCP in Yeastar V25.1?
MCP, the Model Context Protocol, is an open standard for connecting AI assistants to tools and data. In V25.1 you can add MCP servers to the PBX, and the AI Receptionist can use the tools they offer during a call.
How is MCP different from the custom tools in V24.3?
A custom tool is one HTTP request you define yourself. An MCP server offers a bundle of tools through one connection, maintained by whoever runs that server.
Are MCP tool calls logged?
Yes. Each MCP tool call is logged in the call records with the server name, tool name, status, request parameters and response.
Where are Yeastar's release notes for V25.1?
In Yeastar's release notes for 84.24.0.30.