ictdialer_list_campaigns
List campaigns
List the outbound campaigns on the 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 ICTDialer outbound auto-dialer campaigns, and start and stop them when writes are on.
Connects an assistant to an ICTDialer auto-dialer server to list outbound campaigns, check status, read summaries and per-call results, and optionally start…
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 ICTDialer — the cloud auto-dialer and predictive-dialer platform from ICT Innovations. ICTDialer.com is the hosted edition of ICTContact and runs the same engine, so this server speaks that API.
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 ICTDIALER_MCP_ALLOW_WRITE=true:
The server is read-only by default. Starting a campaign begins live outbound
calling and can cost real money, so ictdialer_start_campaign and
ictdialer_stop_campaign are not registered at all unless you set
ICTDIALER_MCP_ALLOW_WRITE=true.
ICTDialer exposes 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 ICTDialer, ICTContact, ICTBroadcast, ICTFax and ICTPBX. Learn more at ictdialer.com.
MIT licensed. Issues and PRs welcome at github.com/ictinnovations/ictdialer-mcp.
Source: README.md at commit c8e687d
List campaigns
List the outbound campaigns on the 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 ictdialer-mcp # no installnpm install -g ictdialer-mcp{ "mcpServers": { "ictdialer": { "command": "npx", "args": ["-y", "ictdialer-mcp"], "env": { "ICTDIALER_BASE_URL": "https://your-ictdialer", "ICTDIALER_USERNAME": "admin", "ICTDIALER_PASSWORD": "your-password" } } }}