yeastar-mcp
Related Servers
Alternatives to yeastar-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage dSIPRouter operations such as endpoint groups, carrier groups, inbound mappings, and call data retrieval through natural language.Apache 2.0- AlicenseAqualityBmaintenanceProvides read-only access to Yeastar P-Series PBX System APIs, enabling querying of extensions, groups, trunks, routes, IVR menus, ring groups, queues, live call and agent status, contacts, call detail records, reports, and system metadata for AI assistants.262Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.10017 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and MCP clients to audit, monitor, diagnose, and safely manage Grandstream UCM phone systems, including extension status, call reports, site reconciliation, and confirmed test calls or admin edits.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Veeam Backup & Replication infrastructure through natural language, allowing monitoring, management, and troubleshooting of backup jobs, sessions, and restore points.MIT

ictpbx-mcpofficial
AlicenseAqualityBmaintenanceThis MCP server enables AI assistants to read PBX state—extensions, DID numbers, SIP trunk providers, tenants, and live statistics—from ICTPBX via the ICTCore REST API, without placing calls or changing configuration.543 npm16MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct roles: list/search/get/query separate basic listing, lookup, single-detail, and batch-detail reads, while prepare_change, prepare_operation, prepare_raw, and prepare_rollback are differentiated by config changes, live operations, raw escape hatch, and rollback. Some overlap remains between yeastar_read and the catalog-based read tools, since read can also retrieve status/report data that overlaps conceptually with get/query/list.
All tools use a consistent yeastar_ snake_case prefix, and the core workflow names (prepare_change, apply_change, cancel_change, pending_changes, audit_log) are highly predictable. Minor inconsistency comes from mixing verb-style names (list, search, get, query, read) with noun-style names (overview, catalog, audit_log), though the pattern remains readable.
Fifteen tools is at the upper end of the ideal range but appropriate for a PBX management server that separates read operations, safe preparation, application, cancellation, rollback, and auditing. Each tool appears to serve a distinct part of the configuration/live-operation lifecycle rather than duplicating another.
The server covers discovery (overview, catalog), read workflows (list, search, get, query, read), safe write workflows (prepare/apply/cancel/pending), rollback, raw endpoint escape, and audit logging. This provides broad CRUD/lifecycle coverage for PBX configuration and live operations with no obvious dead ends, especially because generic read and raw/prepare paths cover uncatalogued endpoints.