Skip to main content
Glama

Related Servers

Alternatives to ictcontact-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables 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.
      4
      220 npm
      16
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      234 npm
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read ICTCRM contact groups and, when write access is enabled, create or delete contacts and add contacts to campaigns.
      1
      226 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage and monitor a Five9 contact center, including campaigns, agents, IVR flows, call statistics, and reports through MCP.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      This 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.
      5
      222 npm
      16
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides 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
      1
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues