Use 3CX MCP to connect your AI and PBX data, creating reports on questions that matter.
Standard 3CX reports cover the metrics most teams need day-to-day. But sometimes you need to go further. Which hours caused a drop in service level? Were abandoned calls caused by high demand or unavailable agents? Which call journeys involved the most transfers?
With the 3CX MCP Server, you can connect a compatible AI application to 3CX and ask these questions in natural language. The AI can retrieve your available PBX data, analyse it and return the result in an easy to understand format, such as a spreadsheet or an infographic.
This does not replace native 3CX reports or the Data Connector. It adds another option for custom, permission-aware reporting without first building a complete BI workflow.
Turn PBX Data Into Custom Reports
MCP gives AI applications controlled access to tools exposed by 3CX. Instead of exporting data to a spreadsheet and analysing it manually, you can ask a business question and let the connected application retrieve the permitted information it needs.
For example, you could ask: Compare Support queue performance by hour for the last 30 days. Show answer rate, wait time and abandonment, and highlight the three periods that need the most attention.
You can then follow up immediately with questions such as which calls contributed to a particular peak or whether the result changes when after-hours calls are excluded. The important part is MCP follows the permissions of the 3CX user who authorises the connection. A department manager only works with the data available to them, while a user with broader access can report across a wider scope.
For the full list of available MCP tools, permissions and connection requirements, see the 3CX MCP Tools and Permissions guide and the MCP Server connection guide.
3CX Data Connector versus 3CX MCP Server
MCP is not intended to replace every reporting option in 3CX.
- Use native 3CX reports when the metric and filters you need already exist. They remain the simplest option for standard operational reporting.
- Use MCP when you want to ask more specific questions, combine permitted data in a different way or turn an investigation into a reusable report.
For larger reporting environments that need continuous historical data, fixed dashboards or analysis across multiple PBXs, the 3CX Data Connector remains the better fit.
Three Ways to Use 3CX MCP Server Reporting
1. Ask Questions on Demand
The simplest use case is an ad-hoc investigation. Connect your AI application to 3CX, describe what you want to understand and refine the result through follow-up questions. This can help managers investigate things such as:
- Queue performance and service-level issues
- Call transfers and longer customer journeys
- Staffing or coverage gaps
- Unusual call volumes or routing behaviour
Rather than working through several CSV exports, the conversation can move directly from what happened to why it happened.
2. Create Scheduled Digests
A useful report can also become a recurring digest. For example, a Customer Service Manager could receive a daily summary showing call volume, answer rate, service level and the biggest exceptions compared with recent performance.
Scheduling is handled by the AI application or platform running the MCP workflow, rather than by the native 3CX report scheduler. This makes it possible to deliver a short report focused on what changed and what deserves attention, rather than another long list of call records.
3. Add AI to a Dashboard
MCP can also sit behind an internal reporting dashboard. Fixed cards can show agreed KPIs while an AI layer answers follow-up questions or generates a fresh analysis for the signed-in user's permitted scope.
For larger or continuously refreshed dashboards, use the 3CX Data Connector as the underlying reporting store and MCP as the interactive layer.
Start With One Useful Report
The easiest way to start is to avoid rebuilding your reporting environment. Pick one recurring question that currently requires a CSV export, spreadsheet work and manual explanation. Ask it through the 3CX MCP Server, compare the result with a known 3CX report and refine the prompt until it gives you the output you need.
A few good starting points are:
- Identify the hours where a queue regularly misses its service-level target
- Find call journeys with unusually high numbers of transfers
- Compare demand with periods where no agents were available
- Create a short daily digest of the biggest changes and exceptions
For reporting use cases, start with the lowest required user permissions and read-only tools. The connected AI application should only have access to the information needed for the report.
The native MCP endpoint is introduced with V20 Update 10 Alpha. Refer to the 3CX MCP Server guide for connection steps, requirements and supported clients.
Join the Discussion
Join the 3CX discussion in our dedicated Partner or Customer Forums. Follow us on X and LinkedIn to stay up to date on the latest 3CX news and feature releases.
