Skip to main content
Glama
theYahia

@theyahia/voximplant-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @theyahia/voximplant-mcp

No user-submitted related servers found.

    Related Servers

    • planfix-mcp

      theYahia
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Planfix API enabling task, project, contact, and comment management with 10 tools and 2 skills.
      20
      26 npm
      3
      MIT
    • VoIPbin MCP Server by voipbin

      VoIPbin MCP Serverofficial

      voipbin
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
      52
      1
      MIT
    • CallMCP by CallMCP

      CallMCPofficial

      CallMCP
      A
      license
      Not graded
      quality
      D
      maintenance
      A single MCP server that provides a provider-neutral 14-tool contract for telephony operations (calls, SMS, recordings, transcripts, and number lifecycle), supporting hosted, fully local, or bring-your-own-key backends.
      1
      MIT

    • TELNYX MCP Server

      tomaitagaki
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for TELNYX integration, enabling AI assistants to send SMS messages, make voice calls, and handle incoming communications via webhooks.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 23 tools

    Disambiguation2/5

    There is direct overlap between get_account_info and skill-account-info, which appear to expose the same account information, and get_call_history and skill-call-history are also very similar. Additionally, get_acd_state, get_sq_state, and get_queues all touch queue/state concepts and may be confused without reading carefully.

    Naming Consistency3/5

    Most tools follow a clear get_* pattern, with action verbs like send_, start_, and update_ for mutations. However, skill-account-info and skill-call-history break the convention using hyphenated noun phrases, creating a noticeable inconsistency in an otherwise predictable naming scheme.

    Tool Count3/5

    23 tools is on the heavy side and borders on overwhelming for a single MCP server. The breadth is somewhat justified by Voximplant's wide platform surface, but duplicate account-info and call-history tools inflate the count without adding real capability.

    Completeness2/5

    The tool surface is heavily read-oriented: most resources are queryable, but mutation coverage is sparse. There is no create/delete/update for users, phone numbers, queues, rules, or scenarios beyond update_scenario, and no way to manage recordings or caller IDs, so agents cannot perform full lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources