Skip to main content
Glama
WYRE-AI

Yeastar MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yeastar MCP Server

No user-submitted related servers found.

    Related Servers

    • CyberQP MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Provides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.
      10
      -

    • UISP MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to monitor Ubiquiti UISP network infrastructure through read-only REST API access to sites, devices, outages, logs, data links, gateways, background tasks, firmware, and speed tests.
      27
      -

    • Brivo Velocity

      ThatGuyinIT
      A
      license
      C
      quality
      A
      maintenance
      Enables Claude to query read-only Brivo access-control data—sites, access points, control panels, users, credentials, schedules, cameras, and more—through MCP tools. It exposes all read-only GET endpoints so users can inspect account information and door status in conversation without write or control actions.
      75
      MIT
    • ictcontact-mcp by ictinnovations

      ictcontact-mcpofficial

      ictinnovations
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to monitor outbound campaigns in ICTContact/ICTDialer, including listing campaigns, checking status, reading summaries and per-call results, and optionally starting and stopping campaigns when write access is enabled.
      4
      28 npm
      16
      MIT

    • hostaway-kit

      stylabs
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to Hostaway PMS data, enabling assistants to answer questions about listings, calendars, reservations, and inbox threads, and generate occupancy, inbox, and completeness reports without writing or sending anything.
      11
      39 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

    A3.8/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool targets a distinct PBX resource or status view, and list/get pairs are clearly separated. Potentially confusable pairs such as trunks vs ITSP trunks, CDR vs call reports, and queue call status vs queue agent status are explicitly distinguished in their descriptions.

    Naming Consistency5/5

    All tools share the yeastar_ prefix and consistently use list_<resource> for collections and get_<resource> for single-item details. Extended names like get_queue_call_status and get_queue_agent_status follow the same predictable resource-plus-modifier pattern.

    Tool Count4/5

    26 tools is high, but the set is a systematic list/get pair for each major PBX resource plus a few dedicated monitoring reads. It sits just above the comfortable range, yet each tool earns its place and the count is not bloated or redundant.

    Completeness4/5

    As a deliberately read-only inspection and monitoring surface, it covers the major PBX objects: extensions, groups, trunks, routes, IVRs, ring groups, queues, contacts, CDR, reports, backups, and certificates. Minor gaps remain around recordings, voicemail message details, and write/provisioning operations, but those appear intentionally excluded.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources