Yeastar P-Series PBX MCP server
MCP server for Yeastar P-Series PBX System API (read-only).
B70/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Yeastar P-Series PBX yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Yeastar P-Series PBX tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add yeastar-mcp -- docker run -i --rm ghcr.io/wyre-ai/yeastar-mcp:v1.0.0
Yeastar P-Series PBX: common questions
- Is Yeastar P-Series PBX MCP server safe?
- Mostly: it is graded B (70/100). Read the Yeastar P-Series PBX safety report
- How do I install Yeastar P-Series PBX?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Yeastar P-Series PBX need an API key?
- Yes. The registry entry asks for
YEASTAR_CLIENT_ID,YEASTAR_CLIENT_SECRET. - Is Yeastar P-Series PBX maintained?
- The last commit was in the last day (2026-09-20). The latest release is v1.0.0.