The JEDWare Statistics API can now be used directly by AI assistants through the Model Context Protocol (MCP), an open standard supported by Claude, ChatGPT, Microsoft Copilot, Cursor and most other AI tools. Instead of writing API requests, you and your colleagues ask questions in natural language:
“How many calls did the support queue lose last week?”
“Compare WhatsApp and Live Chat volume per queue this month.”
“Which agents had the longest talk time yesterday?”
The AI assistant connects to your own 3CX/JEDWare server, picks the right report, fills in the dates and filters, and summarizes the result. All data stays between your server and your AI provider. JEDWare adds no AI of its own and never sees the conversation.
What you need
- JEDWare integration 26.9.1 or newer on the 3CX server. The Support page in the app shows the installed version.
- A JEDWare API key, created once under API in the left menu of the JEDWare app. The key is shown a single time; store it in a password manager. See Managing Statistics API keys.
- The MCP address of your system:
https://<your-3cx-address>/jedware/mcp– your 3CX address exactly as you open the web client, including the port if it has one (hosted systems often use port 5001, for examplehttps://mycompany.my3cx.com:5001/jedware/mcp). Without the port the assistant cannot connect.
What the assistant can access
Reports only, read-only: agent statistics, queue and ring group statistics, group statistics, call reports, talk time, agent status, queue availability, queue callbacks and queue chats (Live Chat, WhatsApp, Facebook, SMS). It can also list your queues, ring groups and extensions so it understands names like “the support queue”. It cannot change any settings, and it only sees what the Statistics API already exposes.
Access control
Access follows the API key. Revoke the key in the JEDWare app and every AI connection made with it stops working within minutes, including sessions that signed in through a browser.