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_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 facet: list_campaigns (enumeration), campaign_status (live run state), campaign_summary (aggregate totals), campaign_result (per-call rows). campaign_summary and campaign_result overlap somewhat in reporting on outcomes, but the aggregate-vs-row distinction is clear enough from the descriptions.
All tools share the ictcontact_ prefix and campaign-related names, with a predictable noun_component pattern for three of them. list_campaigns breaks the noun-first pattern by using a verb prefix, a minor deviation that remains readable.
Four tools is on the thin side for a dialer/campaign integration; the surface covers only read/monitoring operations. It is not extreme, but the set feels like a narrow slice of the domain rather than a well-rounded toolkit.
The surface is entirely read-only: you can list, monitor status, and pull summaries/results, but there is no way to start, stop, create, or control a campaign — despite status tooling explicitly advising polling while a campaign runs. This dead end limits agents to observation only.