Skip to main content
Glama
OITApps

oitvoip-mcp-server

Official
by OITApps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to oitvoip-mcp-server

No user-submitted related servers found.

    Related Servers

    • VoIPBin MCP Server

      nrjchnd
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with VoIPBin's VoIP services, supporting features like call management, agent management, campaigns, conferences, and chat functionality.
      4
      MIT

    • pbx-mcp

      ictinnovations
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that lets AI assistants inspect and control Asterisk and FreeSWITCH PBX systems, enabling natural language queries about live switch status, channels, registrations, and call control.
      10
      30 npm
      16
      MIT

    • Voyp MCP Server

      paulotaylor
      A
      license
      B
      quality
      F
      maintenance
      The Voyp MCP Server enables AI systems to integrate with VOYP's calling capabilities, allowing for secure telephony actions such as making calls, scheduling appointments, and tracking call statuses through the Model Context Protocol.
      7
      9 npm
      10
      MIT

    • five9-mcp

      five9-tam
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server connecting AI assistants to the Five9 contact center, enabling management of campaigns, agents, IVR flows, and reports via natural language.
      MIT

    • warp-mcp

      Ringer
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Ringer WARP platform giving AI agents 135 tools to manage SIP trunking, phone numbers, porting, messaging, billing, and analytics.
      135
      73 npm
      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

    B3.1/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target distinct resources (agents, domains, users, call queues, phone numbers, etc.), but there are a few potentially confusing pairs like `get_call_queue` vs `get_call_queues` and `get_phone_number` vs `get_phone_numbers`, though descriptions clarify the singular/plural distinction.

    Naming Consistency4/5

    The vast majority of tools follow the 'get_<resource>' pattern, with only three exceptions (`login_agent`, `logout_agent`, `test_connection`). This deviation is minor but prevents a perfect score.

    Tool Count4/5

    23 tools is slightly above the typical range for a focused server, but the domain (VoIP management) has many distinct resource types, so the count is reasonable and each tool serves a clear purpose.

    Completeness2/5

    The tool surface is heavily read-oriented with almost all tools being getters. Only two mutation tools exist (login/logout agent). Missing CRUD operations for domains, users, phone numbers, etc., severely limits management capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources