Skip to main content
Glama
Ringer

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to warp-mcp

No user-submitted related servers found.

    Related Servers

    • @saperly/mcp by Saperly

      @saperly/mcpofficial

      Saperly
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Saperly that enables AI agents to provision phone numbers, place calls, send SMS, and manage credentials via 36 tools backed by the Saperly API.
      26 npm
      3
      MIT
    • oitvoip-mcp-server by OITApps

      oitvoip-mcp-serverofficial

      OITApps
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI agents with seamless access to the NetSapiens VoIP platform for user management, call analytics, and system administration.
      23
      4
      -

    • joltsms-mcp-server

      rchanllc
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.
      25 npm
      1
      MIT

    • Karya

      Dashy-E
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents hands to make phone calls, send messages, and handle CRM/task workflows. It runs with a simulated provider for zero-cost testing and can switch to real providers like Twilio and ElevenLabs.
      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
      48 npm
      17
      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

    A3.9/5.0

    Scored across 135 tools

    Disambiguation4/5

    Tools are grouped by domain prefixes (acct_, net_, key_, bill_, msg_, num_, port_, trunk_, team_, cdr_) and nearly every tool has a distinct resource+action purpose. A few near-duplicates exist (acct_get_balance vs bill_get_balance, key_get_audit vs key_get_audit_all, msg_list vs msg_get_stats), but their descriptions explicitly disambiguate them, so an agent should rarely misselect.

    Naming Consistency5/5

    All 135 tools follow a consistent snake_case domain_prefix_verb_noun pattern (e.g. trunk_list_endpoints, msg_create_campaign, port_get_progress). The naming is highly predictable across the entire tool surface, with no mixed conventions or vague verbs.

    Tool Count1/5

    135 tools is far beyond the range that can be considered well-scoped for an LLM agent's tool set. Even though the server covers many domains, this extreme count creates a large selection surface, memory burden, and prompt overhead that outweighs the depth of coverage.

    Completeness5/5

    The tool surface is remarkably comprehensive: accounts, networking, API keys, billing, SMS/10DLC messaging, number inventory, port-in lifecycle, trunk management, team/roles, and CDR analytics all have robust CRUD/lifecycle coverage. The port-in workflow in particular has no obvious dead ends—create through activate, including documents, validation, auto-fix, resubmission, and cancellation.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources