Skip to main content
Glama
MSPbotsAI

ringcentral-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ringcentral-mcp

No user-submitted related servers found.

    Related Servers

    • five9-mcp

      saboor650
      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

    • bvoip-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Bvoip / 1Stream that exposes call-reporting, phone-status, and CRM-extension-mapping endpoints as MCP tools.
      -

    • QCall AI MCP Server

      kapilkarda
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to manage AI voice assistants, place calls, run campaigns, handle contacts and knowledge bases, and read call transcripts. It also provides account, phone number, dialer, and analytics tools through a hosted or local MCP connection.
      25
      MIT
    • Dial MCP Server by GetDial-AI

      Dial MCP Serverofficial

      GetDial-AI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to provision phone numbers, send SMS, place AI voice calls, and react to inbound events via the Dial communication stack, all through MCP tools.
      617 npm
      MIT

    • Genesys MCP

      DigitalVanguardSolutions
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Genesys Cloud platform through MCP tools, resources, and prompts, supporting queues, conversations, users, presence, and analytics with production-ready features like Streamable HTTP and per-request authentication.
      1
      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 13 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action (presence, account, extensions, queues, contacts, call logs, recordings). The only minor overlap is between ringcentral_list_extensions and ringcentral_list_internal_contacts, but their descriptions clearly differentiate account extensions from directory entries.

    Naming Consistency5/5

    All tools follow a consistent ringcentral_<verb>_<resource> pattern, using 'get' for single items and 'list' for collections. The naming is uniformly snake_case and predictable, making it easy to infer the purpose of each tool.

    Tool Count5/5

    Thirteen tools is well-scoped for a RingCentral API server covering account info, extensions, contacts, call logs, and recordings. Each tool has a clear purpose and none feel redundant; the count is in the ideal range for a domain-specific MCP server.

    Completeness4/5

    The surface covers the main read-only resources: presence, account, extensions, phone numbers, queues, contacts, and call logs/recordings. Minor gaps like missing single-phone-number lookup or queue detail endpoints are workable, as the list tools provide sufficient data for most queries.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources