3cx-api-patternslisted

3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com), the Admin Console + client setup flow, the permission model (fully inherited from the 3CX account that approved the connection), and how to discover the live tool surface since 3CX has not published exact tool-name strings.
wyre-technology/msp-claude-plugins · ★ 46 · API & Backend · score 81

Install: claude install-skill wyre-technology/msp-claude-plugins

# 3CX API Patterns ## Overview 3CX added a native MCP server built directly into the PBX, introduced in **3CX V20 Update 10** (announced July 30, 2026 as an **Alpha** release — 3CX's own release notes describe Update 10 Alpha as "intended for testing and evaluation only"). Treat everything in this plugin as based on that Alpha: exact tool names, the permissions reference, and behavior may all shift before 3CX ships Update 10 GA. This is a different project from the older third-party *SSIG-IT/3cx-mcp-server* on GitHub, a community-built MCP server that talks to 3CX's REST API rather than shipping inside the PBX. Do not mix the two up, and do not carry claims from the community project into this one — in particular, its "Enterprise/Enterprise Plus license required" claim is specific to that project and is **not** confirmed for 3CX's native MCP server. ## Anti-triggers - **The community *3cx-mcp-server* project** — different codebase, different tool surface, different auth model (its own API-key setup rather than per-PBX OAuth). Nothing in this plugin describes it, and nothing about it should be assumed here. - **A customer's "the phones are down" ticket** — that's ticket handling in the PSA, not a 3CX MCP call. Use `halopsa-tickets`, `connectwise-psa-tickets`, or `autotask-tickets` to work the ticket itself; come back to this plugin once you need the PBX-side facts. - **WYRE's Conduit vendor catalog** — 3CX has no catalog entry there and, structurally, cannot