ictcontact-mcp
OfficialRelated Servers
Alternatives to ictcontact-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants to monitor ICTDialer outbound campaigns by listing them, checking status, and reading summaries and per-call results, with optional start and stop capabilities when write access is enabled.428 npm16MIT
ictbroadcast-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to monitor ICTBroadcast outbound voice, SMS, and fax campaigns by listing campaigns, checking status, and reading summaries and per-call results, with optional start/stop control when write access is enabled.428 npm16MIT
ictcrm-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to read ICTCRM contact groups and, when write access is enabled, create or delete contacts and add contacts to campaigns.123 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage and monitor a Five9 contact center, including campaigns, agents, IVR flows, call statistics, and reports through MCP.MIT

ictpbx-mcpofficial
AlicenseAqualityBmaintenanceThis MCP server enables AI assistants to read PBX state—extensions, DID numbers, SIP trunk providers, tenants, and live statistics—from ICTPBX via the ICTCore REST API, without placing calls or changing configuration.532 npm16MIT- FlicenseAqualityBmaintenanceProvides read-only access to Yeastar P-Series PBX System APIs, enabling querying of extensions, groups, trunks, routes, IVR menus, ring groups, queues, live call and agent status, contacts, call detail records, reports, and system metadata for AI assistants.26-
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.