ictdialer-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTDIALER_BASE_URL | Yes | Server base URL, without the /rest suffix, e.g. https://your-ictdialer | |
| ICTDIALER_PASSWORD | Yes | Password for that account | |
| ICTDIALER_USERNAME | Yes | API account username | |
| ICTDIALER_TIMEOUT_MS | No | Per-request timeout | 30000 |
| ICTDIALER_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only | false |
| ICTDIALER_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 |
|---|---|
| ictdialer_list_campaignsA | List the outbound campaigns on the ICTDialer server (id and name of each). Start here to find a campaign id. |
| ictdialer_campaign_statusA | Live status of a campaign by id (for example running or stopped). Poll this while a campaign runs. |
| ictdialer_campaign_summaryB | Totals for a campaign: answered, failed, human vs machine and so on. Optionally scope to one agent/user id. |
| ictdialer_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 targets a distinct slice of campaign data: live status, aggregate totals, per-call rows, and the campaign list. The only mild overlap is status vs. summary, both 'campaign-level overview' tools, but descriptions differentiate live state from aggregate metrics well.
All names are snake_case and share the ictdialer_ prefix, with campaign-noun suffixes (status, summary, result). The outlier is ictdialer_list_campaigns, which uses verb_noun while the others use noun_resource ordering, a minor deviation.
Four tools is thin for a dialer server; the surface is entirely read-only monitoring with no control operations. Each tool earns its place, but the scope feels under-built rather than well-scoped.
Only observation is covered; there is no way to create, start, stop, pause, or edit a campaign, nor any contact/list management. An agent can inspect campaigns but hits a dead end for any lifecycle action.