Yeastar P-Series PBX MCP Server

Yeastar P-Series PBX is an MCP integration. MCP server for Yeastar P-Series PBX System API (read-only).

Packages and local setup

The published oci package is ghcr.io/wyre-ai/yeastar-mcp:v1.0.0. Its declared MCP transport is stdio.

The package declares YEASTAR_PBX_DOMAIN (required): This appliance's own domain/IP and port, e.g. https://pbx.example.com:8088. Each customer's PBX is its own instance - there is no shared hosted endpoint.; YEASTAR_CLIENT_ID (required): OAuth-style Client ID, generated in the PBX web portal under Integrations -> API.; YEASTAR_CLIENT_SECRET (required): OAuth-style Client Secret, generated in the PBX web portal under Integrations -> API.; MCP_TRANSPORT: Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.; AUTH_MODE: Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.; LOG_LEVEL: Log verbosity: debug, info, warn, error.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.