ictpbx-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTPBX_BASE_URL | Yes | ICTCore REST base, normally ending in /api, e.g. https://your-ictpbx/api | |
| ICTPBX_PASSWORD | Yes | Password for that account | |
| ICTPBX_USERNAME | Yes | API account email (ICTCore logs in by email) | |
| ICTPBX_TIMEOUT_MS | No | Per-request timeout | 30000 |
| ICTPBX_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ictpbx_pbx_statisticsA | Counts across the PBX: extensions, devices, ring groups, call queues, IVR menus, voicemails, conferences and gateways. Use this first for a quick health picture of the server. |
| ictpbx_list_extensionsA | List SIP extensions on the PBX with their username, name, tenant and account id. Use this to answer 'what extensions exist' or to find an extension's tenant. |
| ictpbx_list_didsA | List DID (inbound phone) numbers on the PBX: the number, whether it is active, its tenant and the contact it is tied to. |
| ictpbx_list_providersA | List the SIP trunk providers (upstream carriers) configured on the PBX: name, host and tenant. |
| ictpbx_list_tenantsA | List the tenants (customer organizations) on this multi-tenant PBX: company, contact and limits. Use this to see who the white-label PBX is serving. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource: tenants, PBX-wide statistics, extensions, DIDs, and providers. There is no meaningful overlap, so an agent can reliably select the correct tool based on the resource it needs.
Tool names mostly follow a consistent ictpbx_list_<resource> pattern, with ictpbx_pbx_statistics being the one deviation. The prefix is uniform and the intent of each name is clear.
Five tools is a well-scoped set for a read-only PBX inventory and health-check server. Each tool covers a meaningful area without excess or redundancy.
The server only provides list and count operations, with no create, update, delete, or search capabilities. While statistics mention many PBX resources, only tenants, extensions, DIDs, and providers have detailed list tools, leaving significant gaps for full PBX management.