dev.wirecat/asterisk-cli
WireCat pbx
Is the WireCat pbx MCP server down? It gave no valid answer in the probe of 2026-11-14: crashed on start. One failed probe is not an outage.
Asterisk calls for agents over MCP. Set up a profile with the pbx CLI first.
crashed on start no valid answer since 2026-11-14 · probed 2026-11-14
MCP error -32000: Connection closed
{"error":{"code":"configuration_error","reason":"config.invalid","message":"no pbx profile on this computer yet — set one up- Run it
- npx -y @wirecat/asterisk-cli@0.4.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/WireCatLabs/asterisk-cli
- Website
- https://wirecat.dev/en/docs/pbx
- Registry
- active, updated 2026-11-14 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- vid2llm dev.vid2llm/mcp · alive
- dev.waxberry/live-translate-mcp · crashed on start
- dev.weakspot/weakspot · alive
- Weavetab dev.weavetab/mcp · crashed on start
- WireCat b24 dev.wirecat/bitrix24-cli · crashed on start
- WireCat Memo dev.wirecat/cli-memo · alive
- WireCat Google Drive dev.wirecat/drive-cli · crashed on start
- WireCat Google Calendar dev.wirecat/gcal-cli · crashed on start
Servers that mention asterisk or wirecat.
- io.github.ictinnovations/pbx-mcp · alive
- WireCat Telegram dev.wirecat/tg-cli · crashed on start
- WireCat Zoom dev.wirecat/zoom-cli · crashed on start
- WireCat MAX dev.wirecat/max-cli · crashed on start
- WireCat WhatsApp dev.wirecat/whatsapp-cli · crashed on start
- WireCat Mail dev.wirecat/mail-cli · crashed on start
- Acme CRM example io.github.leemour/acme-crm-cli · crashed on start
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-14. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.