ictbroadcast-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTBROADCAST_BASE_URL | Yes | Server base URL, without the /rest suffix, e.g. https://your-ictbroadcast | |
| ICTBROADCAST_PASSWORD | Yes | Password for that account | |
| ICTBROADCAST_USERNAME | Yes | API account username | |
| ICTBROADCAST_TIMEOUT_MS | No | Per-request timeout | 30000 |
| ICTBROADCAST_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only | false |
| ICTBROADCAST_MCP_ALLOW_WRITE | No | Unlock start/stop campaign (see Safety) | 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 |
|---|---|
| ictbroadcast_list_campaignsA | List the outbound campaigns on the ICTBroadcast server (id and name of each). Start here to find a campaign id. |
| ictbroadcast_campaign_statusB | Live status of a campaign by id (for example running or stopped). Poll this while a campaign runs. |
| ictbroadcast_campaign_summaryB | Totals for a campaign: answered, failed, human vs machine and so on. Optionally scope to one agent/user id. |
| ictbroadcast_campaign_resultB | Per-call results for a campaign (contact, response, answering-machine detection, DNC), optionally filtered by call status. |
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 4 tools
Each tool has a clearly distinct role: listing campaigns, checking live status, viewing aggregate totals, or inspecting per-call results. The descriptions make the boundaries between status, summary, and result explicit.
All tools use snake_case and a consistent ictbroadcast_ prefix. There is a minor structural deviation between ictbroadcast_campaign_status/summary/result and ictbroadcast_list_campaigns, but the pattern remains readable.
Four tools is a reasonable, focused set for campaign monitoring and reporting. It is slightly thin if the server is intended to cover broader campaign administration, but each tool earns its place.
The set covers the read/reporting side well: list campaigns, check status, get summary totals, and inspect per-call results. However, it lacks campaign lifecycle controls such as start/stop and broader management operations, which are notable gaps for an ICTBroadcast server.