Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Yeastar P-Series PBX

by WYRE-AIversion 1.0.2i★ 2iRuns on your computerRepository ↗
Registry nameio.github.WYRE-AI/yeastar-mcp

How to install

What it does

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

  • Connects Runs on your computer
  • Account or key Needs YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE · 1 setting to fill in (YEASTAR_PBX_DOMAIN)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score18/100

Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Yeastar P-Series PBX. Follow https://mcp.popnx.com/i/wyre-ai-yeastar-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yeastar P-Series PBX for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yeastar": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "YEASTAR_PBX_DOMAIN", "-e", "YEASTAR_CLIENT_ID", "-e", "YEASTAR_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2" ], "env": { "YEASTAR_PBX_DOMAIN": "your-value", "YEASTAR_CLIENT_ID": "your-value", "YEASTAR_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Yeastar P-Series PBX tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Yeastar P-Series PBX key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Yeastar P-Series PBX site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • YEASTAR_PBX_DOMAIN 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.

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "yeastar": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "YEASTAR_PBX_DOMAIN",
            "-e",
            "YEASTAR_CLIENT_ID",
            "-e",
            "YEASTAR_CLIENT_SECRET",
            "-e",
            "AUTH_MODE",
            "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2"
          ],
          "env": {
            "YEASTAR_PBX_DOMAIN": "your-value",
            "YEASTAR_CLIENT_ID": "your-value",
            "YEASTAR_CLIENT_SECRET": "your-value",
            "AUTH_MODE": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Yeastar P-Series PBX and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Yeastar P-Series PBX or shows a Yeastar P-Series PBX tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Yeastar P-Series PBX yet

Yeastar P-Series PBX runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Yeastar P-Series PBX

  • You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)
  • You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)
  • You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yeastar P-Series PBX for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user yeastar --env YEASTAR_PBX_DOMAIN=your-value --env YEASTAR_CLIENT_ID=your-value --env YEASTAR_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e YEASTAR_PBX_DOMAIN -e YEASTAR_CLIENT_ID -e YEASTAR_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/yeastar-mcp:v1.0.2 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Yeastar P-Series PBX tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Yeastar P-Series PBX key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Yeastar P-Series PBX site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • YEASTAR_PBX_DOMAIN 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.

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user yeastar --env YEASTAR_PBX_DOMAIN=your-value --env YEASTAR_CLIENT_ID=your-value --env YEASTAR_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e YEASTAR_PBX_DOMAIN -e YEASTAR_CLIENT_ID -e YEASTAR_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/yeastar-mcp:v1.0.2

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Yeastar P-Series PBX listed as connected

  7. Try it

    Use Yeastar P-Series PBX and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Yeastar P-Series PBX or shows a Yeastar P-Series PBX tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yeastar P-Series PBX for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yeastar": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "YEASTAR_PBX_DOMAIN", "-e", "YEASTAR_CLIENT_ID", "-e", "YEASTAR_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2" ], "env": { "YEASTAR_PBX_DOMAIN": "your-value", "YEASTAR_CLIENT_ID": "your-value", "YEASTAR_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Yeastar P-Series PBX tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Yeastar P-Series PBX key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Yeastar P-Series PBX site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • YEASTAR_PBX_DOMAIN 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.

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Yeastar P-Series PBX settings, YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Yeastar P-Series PBX and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Yeastar P-Series PBX or shows a Yeastar P-Series PBX tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Yeastar P-Series PBX key (create it on the maker’s site) · 1 setting(s) to fill in (YEASTAR_PBX_DOMAIN) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yeastar P-Series PBX for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "yeastar": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "YEASTAR_PBX_DOMAIN", "-e", "YEASTAR_CLIENT_ID", "-e", "YEASTAR_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2" ], "env": { "YEASTAR_PBX_DOMAIN": "your-value", "YEASTAR_CLIENT_ID": "your-value", "YEASTAR_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Yeastar P-Series PBX tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Yeastar P-Series PBX key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Yeastar P-Series PBX site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • YEASTAR_PBX_DOMAIN 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.

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Yeastar P-Series PBX settings, YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE, YEASTAR_PBX_DOMAIN is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Yeastar P-Series PBX and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Yeastar P-Series PBX or shows a Yeastar P-Series PBX tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Yeastar P-Series PBX💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user yeastar --env YEASTAR_PBX_DOMAIN=your-value --env YEASTAR_CLIENT_ID=your-value --env YEASTAR_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e YEASTAR_PBX_DOMAIN -e YEASTAR_CLIENT_ID -e YEASTAR_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/yeastar-mcp:v1.0.2

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "yeastar": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YEASTAR_PBX_DOMAIN",
        "-e",
        "YEASTAR_CLIENT_ID",
        "-e",
        "YEASTAR_CLIENT_SECRET",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2"
      ],
      "env": {
        "YEASTAR_PBX_DOMAIN": "your-value",
        "YEASTAR_CLIENT_ID": "your-value",
        "YEASTAR_CLIENT_SECRET": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "yeastar": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YEASTAR_PBX_DOMAIN",
        "-e",
        "YEASTAR_CLIENT_ID",
        "-e",
        "YEASTAR_CLIENT_SECRET",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2"
      ],
      "env": {
        "YEASTAR_PBX_DOMAIN": "your-value",
        "YEASTAR_CLIENT_ID": "your-value",
        "YEASTAR_CLIENT_SECRET": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "yeastar": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YEASTAR_PBX_DOMAIN",
        "-e",
        "YEASTAR_CLIENT_ID",
        "-e",
        "YEASTAR_CLIENT_SECRET",
        "-e",
        "AUTH_MODE",
        "ghcr.io/wyre-ai/yeastar-mcp:v1.0.2"
      ],
      "env": {
        "YEASTAR_PBX_DOMAIN": "your-value",
        "YEASTAR_CLIENT_ID": "your-value",
        "YEASTAR_CLIENT_SECRET": "your-value",
        "AUTH_MODE": "your-value"
      }
    }
  }
}

Values you fill in

  • YEASTAR_PBX_DOMAIN required env
    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 secret required env
    OAuth-style Client ID, generated in the PBX web portal under Integrations -> API.
  • YEASTAR_CLIENT_SECRET secret required env
    OAuth-style Client Secret, generated in the PBX web portal under Integrations -> API.
  • MCP_TRANSPORT env
    Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE secret required env
    Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL env
    Log verbosity: debug, info, warn, error

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
1.0.2
Categoryi
Other
Published to registryi
Oct 22, 2026
Code last changedi
Nov 12, 2026
Maker
WYRE-AI
Packages
oci: ghcr.io/wyre-ai/yeastar-mcp:v1.0.2
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account WYRE-AI, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 7 days ago

  • ! Caution

    Has a licence

    GitHub could not identify the licence type; open the file to check

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wyre-ai-yeastar-mcp.svg)](https://mcp.popnx.com/en/servers/wyre-ai-yeastar-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 91% of the other 20653 servers in this category
  • Published to the registry more recently than 61% of the other 20653 servers in this category
  • Basic checks equal to or better than 46% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Yeastar P-Series PBX safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: YEASTAR_CLIENT_ID, YEASTAR_CLIENT_SECRET, AUTH_MODE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 7 days ago, and the latest version (1.0.2) reached the registry 28 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Yeastar P-Series PBX
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks2/34/44/44/41/44/4
LicenseNOASSERTIONAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Yeastar MCP Server

MCP server for the Yeastar P-Series PBX System OpenAPI - read-only visibility into extensions, extension groups, trunks, inbound/outbound routes, IVR menus, ring groups, queues (including live call/agent status), the company contact directory, call detail records (CDR), call reports, backup metadata, and certificate metadata, for AI assistants and the WYRE Conduit gateway.

Appliance/Edition Scope

This connector targets the P-Series Appliance Edition's OpenAPI, base path `openapi/v1.0`. Per Yeastar's own developer docs (help.yeastar.com, "P-Series Appliance Edition Developer Guide"), the API is only supported on:

  • Hardware models P550, P560, and P570 running PBX firmware 37.7.0.16 or later. Other Appliance Edition hardware (e.g. P510) is not documented as supporting the API at all - the docs state functionality "is only supported on P550, P560, and P570" without qualification.
  • The docs do not describe any narrower per-endpoint model restriction beyond that - every endpoint this connector implements is covered by the same P550/P560/P570 + firmware-37.7.0.16+ statement.

Cloud Edition is a separate product with its own developer guide and its own OpenAPI surface (same openapi/v1.0 base path structure, firmware requirement documented as 84.7.0.17+), which this connector's request/response shapes were not independently verified against - Appliance and Cloud Edition guides diverge in places (e.g. Cloud Edition additionally documents a v2.0 CDR surface not covered here). If a customer runs Cloud Edition, treat this connector as unverified, not confirmed-incompatible - most of the base OpenAPI mechanics (token exchange, response envelope, pagination) are described identically in both guides, but no endpoint here has been tested against a live Cloud Edition instance.

Software Edition (self-hosted, non-appliance) and any other P-Series variant are out of scope - not mentioned in the Appliance Edition API-support statement above, and not evaluated for this connector.

If a customer's actual hardware/edition is unknown, verify against the PBX web portal (Settings -> About, or the model shown in yeastar_get_system_information) before assuming this connector will work - a PBX outside P550/P560/P570 (Appliance) or Cloud Edition will very likely reject get_token outright with the API feature toggle unavailable in its portal at all.

Authentication

Each Yeastar P-Series PBX is its own appliance, with its own domain/IP and its own credentials - there is no shared hosted API endpoint. A customer enables the API themselves in their PBX's web portal (Integrations -> API, toggle "API" on) and generates a Client ID and Client Secret there. This is not a browser-based OAuth consent flow - the customer pastes the resulting Client ID/Secret directly into the connect form, the same shape as this fleet's other self-hosted/BYO-instance connectors (e.g. Hudu, IT Glue), not the shared-app Authorization Code flow used for SaaS vendors like Cork.

This connector exchanges the Client ID/Secret for a short-lived access token itself - it never proxies them directly into a PBX request. Per Yeastar's docs (POST /openapi/v1.0/get_token), the wire format is genuinely {"username": " ", "password": " "} - Yeastar's own docs are explicit that these fields *are* the Client ID/Secret ("obtain the username from the Client ID on PBX web portal"), not a separate credential; this connector preserves that field naming rather than renaming it, since it's what the vendor's API actually expects on the wire.

Token lifetime and caching. Access tokens expire after 30 minutes; refresh tokens after 24 hours. Yeastar also caps each application to 8 simultaneous valid tokens. Because of that cap, this connector does not mint a fresh token on every tool call - src/client.ts caches the access token in memory, keyed by appliance + Client ID + Client Secret, and reuses it across calls until it's within 60 seconds of expiring. On a TOKEN EXPIRED response (errcode 10004), it transparently mints a fresh token and retries the failed call exactly once. This is a deliberate deviation from the pattern in this fleet's other connectors (which mint per-request or hold a single static key) - it exists because Yeastar's token model genuinely requires it, not as an optimization for its own sake: without caching, any session making more than 8 tool calls within a 30-minute window would start failing with MAX LIMITATION EXCEEDED (errcode 60002) from Yeastar itself.

In gateway mode, the three credential fields arrive per-request via X-Yeastar-Pbx-Domain / X-Yeastar-Client-Id / X-Yeastar-Client-Secret headers, injected by the Conduit gateway. A /mcp request missing any of those headers is rejected with 401 and does not fall back to YEASTAR_* in the process environment. In local/stdio mode, and in HTTP AUTH_MODE=env, they're read from YEASTAR_PBX_DOMAIN / YEASTAR_CLIENT_ID / YEASTAR_CLIENT_SECRET.

HTTP also requires service-to-service auth. With CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The header value is t= ,v1= . The MAC is HMAC-SHA256 over the ASCII message t= (the same t= prefix that appears in the header), keyed by CONDUIT_S2S_SECRET, and encoded as lowercase hex. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401 before vendor credentials are read. The secret is never written to logs. /health and /healthz stay unauthenticated and do not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

Request limits
  • HTTP request bodies are capped at 256 KiB (262144 bytes). After the X-Gateway-S2S check passes (and, in gateway mode, the X-Yeastar-* credential headers are present), a Content-Length above the cap returns 413 with a JSON-RPC error; bodies without Content-Length are capped by the MCP SDK transport. Unauthenticated requests still get 401 first.
  • tools/call arguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return a fixed isError tool result ("Tool input exceeds the maximum of 10000 elements") that does not echo the tool name, and are never dispatched.

These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).

Every request also passes a mandatory `User-Agent: OpenAPI` header - Yeastar's API rejects requests missing it (errcode 40002, "PARAMETER ERROR").

Defensive field-stripping. Trunk configuration commonly carries SIP registration secrets (auth/register passwords) inline in the same object a read returns, and Yeastar's schema for these objects isn't machine-verifiable from the docs alone. Every response from every tool in this connector - not just trunk tools - passes through stripSecretFields() before it ever reaches the model: any object key matching /secret|password|pwd/i, at any depth, is dropped. This is a blanket safety net on top of, not instead of, the endpoint-level exclusions below (extension/getpassword and conference/viewpassword are never called at all).

Credential-scope finding

Structurally verified (this codebase): this connector's src/client.ts implements exactly one HTTP verb function, doGet - there is no doPost/doPut/doDelete anywhere in this codebase, so it is *incapable* of issuing a write/control/delete request to the PBX regardless of what the credential itself is permitted to do. src/__tests__/tool-scope.test.ts pins the exact 26-tool set and asserts no tool name matches a write/control/credential-exposing token list.

Vendor-documented, not independently verified: whether the PBX's own admin portal offers any way to scope a Client ID/Secret pair to read-only access is not documented. Per help.yeastar.com's "Enable Yeastar P-Series PBX API" page, enabling the API surfaces exactly one toggle ("API" on/off) plus an optional IP-restriction allowlist and status-monitor configuration - no permission-group, role, or scope selection is described anywhere in that flow. This differs from e.g. Cisco Duo (cisco-duo-mcp), where the vendor's own admin panel offers explicit Grant Read Resource / Grant Write Resource toggles per integration. The practical implication: a Client ID/Secret pair generated for this connector is, as far as Yeastar's own documentation shows, capable of the PBX's full write/control API even though this connector's code never exercises that capability. The only vendor-side compensating control documented is the optional IP-restriction allowlist (scope the credential to only be usable from Conduit's egress IP(s)) - recommend enabling it. If a narrower credential-scoping mechanism does exist and simply isn't documented publicly, it wasn't found during this connector's build and should be treated as unconfirmed.

Configuration

Env varDescription
YEASTAR_PBX_DOMAINThis appliance's own domain/IP and port, e.g. https://pbx.example.com:8088 (default OpenAPI port is 8088). A bare host with no scheme is treated as https.
YEASTAR_CLIENT_IDOAuth-style Client ID, generated in the PBX web portal under Integrations -> API.
YEASTAR_CLIENT_SECRETOAuth-style Client Secret, generated in the same place.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (default, reads the vars above) or gateway (credentials arrive per-request via X-Yeastar-Pbx-Domain/X-Yeastar-Client-Id/X-Yeastar-Client-Secret). Gateway mode returns 401 when any of those headers is missing and never falls back to YEASTAR_*. The container image and Compose default to gateway.
CONDUIT_S2S_SECRETRequired to start the HTTP transport. The process logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, replace-me, your-s2s-secret, and the other public example values). Compose will not start when it is unset. Never commit a real value.
MCP_ALLOW_INSECURE_DEVSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) refuses to start. A known placeholder secret still refuses to start when this flag is set.
MCP_HTTP_HOSTBind address when a real CONDUIT_S2S_SECRET is set. Unset keeps the historical 0.0.0.0 bind. The container image and Compose set 0.0.0.0 inside the container and publish the host port on 127.0.0.1. Without a secret, the insecure-dev bypass listens on 127.0.0.1 only and refuses a non-loopback value.
MCP_HTTP_PORTHTTP port. Defaults to 8080.
LOG_LEVELdebug \info (default) \warn \error.

Tools

All 26 tools are read-only. yeastar_get_trunk is additionally classified sensitive in Conduit's VENDOR_TOOL_CONFIG given trunk config's proximity to telephony secrets, even after field-stripping.

System
  • yeastar_get_system_information - this appliance's model, firmware version, hostname.
  • yeastar_get_system_capacity - current usage against licensed extension/trunk/concurrent-call capacity.
Extensions
  • yeastar_list_extensions - list extensions with basic info and per-device online/presence status.
  • yeastar_get_extension - full detail for a single extension (never includes its password).
Extension Groups
  • yeastar_list_extension_groups - list extension groups.
  • yeastar_get_extension_group - full detail (member extensions) for one group.
Trunks
  • yeastar_list_trunks - list configured trunks.
  • yeastar_get_trunk - full detail for a single trunk, with secret-shaped f

Only the beginning is shown; read the rest in the repo