Tools that support custom headers connect with the API key directly. Add this to the tool’s MCP configuration (the exact file or menu varies per tool):
{
"mcpServers": {
"jedware": {
"url": "https://<your-3cx-address>/jedware/mcp",
"headers": { "X-Api-Key": "jed_your-key-here" }
}
}
}
- Claude Desktop / Claude Code: Settings > Connectors / MCP servers, or the
.mcp.jsonfile in a project. - Cursor: Settings > MCP > Add server (choose “Streamable HTTP”).
- Any other client works the same way: transport Streamable HTTP, the URL above, and the
X-Api-Keyheader.
After connecting, the assistant sees 14 JEDWare tools. Try “List my queues”. If that returns your queue names, everything works.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| 401 Unauthorized | Wrong or revoked key, or a key created for a different customer. Keys are per system; create one in the JEDWare app for this installation. |
| 404 Not Found | The integration on this server predates the MCP feature. Update the integration. |
| The assistant guesses wrong queue numbers | Ask it to “list the queues first”. The discovery tools exist exactly for this. |
New to the feature? Start with Connect your AI assistant to JEDWare.