Connect your AI assistant to JEDWare

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

1. A JEDWare integration updated in September 2026 or later. Your JEDWare contact can confirm the version.
2. A JEDWare API key, created once under API in the JEDWare app sidebar. The key is shown a single time; store it in a password manager. See Managing Statistics API keys.
3. The MCP address of your system: https://<your-3cx-address>/jedware/mcp

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.

Connect your assistant

• Connecting Claude Desktop, Claude Code, Cursor and other MCP clients
• Connecting claude.ai and ChatGPT (web connectors)
• What can I ask? Available data and examples