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_statusA | 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_resultA | 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 targets a distinct concept: listing campaigns, live status, per-call results, and aggregate totals. Campaign_result and campaign_summary are related but clearly separated by per-call versus totals.
Names follow a consistent ictbroadcast_ prefix and mostly use a noun-based pattern (campaign_result, campaign_status, campaign_summary). The one verb-based name, ictbroadcast_list_campaigns, is a minor deviation but still clear.
Four tools is well-scoped for a campaign monitoring/analytics server. Each tool covers a necessary piece without unnecessary bloat.
The set covers the core campaign monitoring workflow: discover campaigns, check live status, view summary totals, and inspect individual call results. It lacks management operations like create/update/stop, but those may be outside the server's apparent read-only purpose.