3CX MCP

3CX + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the 3CX API. Not affiliated with, endorsed by, or sponsored by 3CX Ltd.

[3CX demo - animated preview]

_{▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.}

Run every client's 3CX phone system from one CLI: trunk, version, licence and backup health across the whole fleet, plus the full Configuration API on any single PBX. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

For ChatGPT, run threecx-mcp --transport http with THREECX_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly and speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: docs/which-agent.md.

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download 3CX MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every 3CX release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills/plugin install threecx@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the 3CX Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.ps1 | iex. Then authenticate per the README and run threecx-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.sh)

The installer drops both threecx-cli (the CLI) and threecx-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

threecx-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threecx/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update threecx@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see mcp-install.md and docs/which-agent.md for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/threecx --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/threecx --force

Hermes speaks MCP natively, so it can also use the threecx-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the threecx skill from https://github.com/servosity/msp-skills/tree/main/skills/threecx. The skill defines how its required CLI (threecx-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your 3CX portal):

THREECX_CLIENT_ID=<value> THREECX_CLIENT_SECRET=<value> THREECX_FQDN=<value> threecx-cli doctor

doctor checks config, paths, and API reachability, and reports whether credentials are loaded - it does not validate them. Run a read command to confirm the credential actually works end-to-end.

What this skill does

Register each client PBX once (threecx-cli fleet add acme --fqdn acme.3cx.us --client-id 900 --env-prefix THREECX_ACME; the API key stays in THREECX_ACME_CLIENT_SECRET, never in a file). The fleet commands query every registered PBX live and in parallel; a PBX that cannot be read gets its own error row instead of stopping the run. Any generated command targets one PBX with --pbx <name>.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Every other 3CX tool we know of, from the admin console to 3CX's own MCP preview, the 3cx-xapi CLI and SSIG-IT/3cx-mcp-server, talks to one phone system per connection. An MSP's question is about the fleet: which of 40 clients has a trunk down this morning.

This skill keeps a local registry of every client PBX, each with its own API credential, and runs the health questions against all of them at once: fleet health rates each PBX pass, warn, fail or unknown on version, licence, backup, trunks, disk, services and capacity, and names each missing input instead of reading it as healthy. fleet changes compares saved runs, so trunks that went down or came back, version bumps, renewals and stale backups show up as a diff. For one PBX, sync mirrors its configuration into local SQLite for offline search.

The pain this closes

MSPs and VoIP resellers run one 3CX PBX per client, and 3CX gives them one admin console per PBX. A dead SIP trunk, a lapsed maintenance plan or a backup that stopped running is usually found when the client calls. The need is real enough that resellers build their own pollers: see the 3CX forum thread on centralized monitoring for 3CX instances (October 2025), where a partner describes checking every instance each minute and opening tickets.

• fleet health: the morning check, one row per client with the reason for every warn or fail.
• fleet trunks --offline: every trunk that is down, misconfigured or unknown, with certificate days left.
• fleet licences --within 60d: the renewals pipeline, soonest first, with seat headroom.
• fleet backups --problems: stale, unscheduled or shrinking backups.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, on Plus, Pro, Team, Business, Enterprise, and Education plans (Free tier does not yet expose Developer Mode). ChatGPT connects to remote MCP servers over HTTPS, not local stdio binaries. The 3CX MCP server runs locally over stdio by default. Its HTTP mode (threecx-mcp --transport http) serves http://127.0.0.1:7777/mcp, refuses to start until THREECX_MCP_HTTP_TOKEN is set, requires Authorization: Bearer <token> on every request, and needs --tls-cert/--tls-key for any other address. See mcp-install.md. Step-by-step in mcp-install.md.

Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?

Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.

Do I need to know how to code?

No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your 3CX credentials once.

Is my 3CX data safe?

Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.

Which 3CX versions and licences does this need?

3CX V20 or later with the Configuration API, which 3CX documents as needing an 8SC or higher licence. On each PBX, create an API client under Admin Console > Integrations > API with Configuration API access and the department and role your workflow needs; the client ID is the DN number shown there and the API key is shown once. A PBX that refuses the token gets an error in its own row.

Does it change anything on my clients' phone systems?

The fleet commands only read. The single-PBX commands cover the whole Configuration API, including writes such as restarting services or rebooting phones. In the MCP server every write returns a preview until the agent sends confirm: true; on the CLI, preview any write with --dry-run first, which sends nothing at all. THREECX_MCP_READ_ONLY=1 removes every MCP tool that can write.

Where do the API keys live?

In one environment variable per PBX, <PREFIX>_CLIENT_SECRET (the prefix is fleet add --env-prefix, default THREECX_<NAME>), or for a single PBX THREECX_CLIENT_SECRET. The fleet registry stores the prefix, never the key. Commands that mint a credential, such as conference-settings generate-api-key, print a notice in place of the new value, so a key never lands in an agent transcript.

What does it cost?

Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.

Safety model

The strongest control is the scope you grant the 3CX credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.

Status

Beta. Validated against the 3CX API surface and being validated with MSPs running it live against their own production tenant in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.

Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).

Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-10-29.