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_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 has a clearly distinct purpose: listing campaigns, checking live campaign state, viewing aggregate totals, and inspecting individual call results. There is no meaningful overlap or risk of selecting the wrong tool for a monitoring step.
All tools share the ictdialer_ prefix and most use ictdialer_campaign_*, but ictdialer_list_campaigns is verb-first while the others are noun-attribute names. This is a minor deviation from a fully consistent verb_noun pattern, but the names remain predictable and readable.
Four tools is a well-scoped count for a focused campaign monitoring server. Each tool covers a distinct stage of the workflow: discover campaigns, check status, get aggregate stats, and drill into results.
The set covers the core read-only monitoring workflow well: list, status, summary, and per-call details. Minor gaps exist, such as no agent listing to support the optional user-id scoping and no campaign detail endpoint, but these do not block the primary use case.