ictcontact-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTCONTACT_BASE_URL | Yes | Server base URL, without the /rest suffix, e.g. https://your-ictcontact | |
| ICTCONTACT_PASSWORD | Yes | Password for that account | |
| ICTCONTACT_USERNAME | Yes | API account username | |
| ICTCONTACT_TIMEOUT_MS | No | Per-request timeout in milliseconds | 30000 |
| ICTCONTACT_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only. Set to 'true' to enable. | false |
| ICTCONTACT_MCP_ALLOW_WRITE | No | Unlock start/stop campaign (see Safety). Set to 'true' to enable write tools. | 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 |
|---|---|
| ictcontact_list_campaignsA | List the outbound campaigns on the ICTContact / ICTDialer server (id and name of each). Start here to find a campaign id. |
| ictcontact_campaign_statusA | Live status of a campaign by id (for example running or stopped). Poll this while a campaign runs. |
| ictcontact_campaign_summaryB | Totals for a campaign: answered, failed, human vs machine and so on. Optionally scope to one agent/user id. |
| ictcontact_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 purpose: list_campaigns enumerates campaigns, campaign_summary returns aggregate totals, campaign_status gives live state, and campaign_result provides per-call details. No two tools overlap in a way that would cause an agent to select the wrong one.
All tool names use snake_case and share the 'ictcontact' prefix, but the pattern is mixed: 'list_campaigns' follows verb_noun while the other three are noun_noun (campaign_summary, campaign_status, campaign_result). This is readable but not fully consistent.
With 4 tools, the server is tightly scoped to campaign monitoring and reporting. Each tool covers a necessary query type without redundant or bloated surface area.
The tool set covers the core campaign workflow: discover campaigns, get summary stats, check live status, and drill into individual results. Minor gaps exist (no detailed campaign metadata or broader call-record export), but the primary monitoring use case is well covered.