ictcontact_list_campaigns
List campaigns
List the outbound campaigns on the ICTContact / ICTDialer server (id and name of each). Start here to find a campaign id.
Takes no parameters.

io.github.ictinnovationsPublished by GitHub account ictinnovationsv0.1.1Updated Oct 26, 2026
Monitor ICTContact / ICTDialer outbound campaigns, and start and stop them when writes are on.
Monitors ICTContact / ICTDialer outbound calling campaigns and, when writes are enabled, starts and stops them.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
A Model Context Protocol server for ICTContact and its hosted edition ICTDialer.com — the same contact-center engine from ICT Innovations.
It lets an AI assistant monitor outbound campaigns — list them, check status, read summaries and per-call results — and, only when you turn writes on, start and stop them.
Requires Node.js 18 or newer.
Read tools are always available:
Write tools appear only when ICTCONTACT_MCP_ALLOW_WRITE=true:
The server is read-only by default. Starting a campaign begins live outbound
calling and can cost real money, so ictcontact_start_campaign and
ictcontact_stop_campaign are not registered at all unless you set
ICTCONTACT_MCP_ALLOW_WRITE=true.
ICTContact and ICTDialer expose a form-encoded RPC API at {base}/rest/<Method>.
Each call carries the account username and password; the server sends those for
you. There is no separate token to provision.
Built by Tahir Almas at ICT Innovations — the team behind ICTContact, ICTDialer, ICTBroadcast, ICTFax and ICTPBX. Learn more at ictcontact.com and ictdialer.com.
MIT licensed. Issues and PRs welcome at github.com/ictinnovations/ictcontact-mcp.
Source: README.md at commit b7162a9
List campaigns
List the outbound campaigns on the ICTContact / ICTDialer server (id and name of each). Start here to find a campaign id.
Takes no parameters.
Campaign status
Live status of a campaign by id (for example running or stopped). Poll this while a campaign runs.
campaign_idrequiredCampaign summary
Totals for a campaign: answered, failed, human vs machine and so on. Optionally scope to one agent/user id.
usr_idcampaign_idrequiredCampaign call results
Per-call results for a campaign (contact, response, answering-machine detection, DNC), optionally filtered by call status.
statuscampaign_idrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx -y ictcontact-mcp # no installnpm install -g ictcontact-mcp{ "mcpServers": { "ictcontact": { "command": "npx", "args": ["-y", "ictcontact-mcp"], "env": { "ICTCONTACT_BASE_URL": "https://your-ictcontact", "ICTCONTACT_USERNAME": "admin", "ICTCONTACT_PASSWORD": "your-password" } } }}