voicegw mcp). Connect an MCP-compatible coding agent and check gateway health, query costs and latency, or create and read back projects, in natural language.
Tool surface
The server exposes 25 tools across five categories. Ten are visible by default; the rest needVOICEGW_MCP_ADMIN=1 set on the server process.
The default set is the framework-agnostic surface: reads (health, costs, latency, logs, models, projects) plus project and rate-card writes. The admin set is the legacy provider-config surface (add_provider, test_provider, the per-project vg_* key tools) plus every destructive delete. It stays admin-gated because VoiceGateway no longer constructs a provider class to route a request: attach()/guard() meter the native STT/LLM/TTS instance you pass in, by model_id, and never touch these classes. What still runs in production is health_check() (reached here through test_provider / vg_test_provider_key, and also by voicegw doctor and POST /v1/providers/{id}/test).
Every
delete_* tool uses a two-phase confirmation: call it with confirm=false (the default) to get a CONFIRMATION_REQUIRED error carrying an impact preview, then call again with confirm=true.
Quick start
mcp extra: the server ships inside dashboard. livekit is required too, even for Pipecat-only agents: every voicegw subcommand imports it at CLI startup. See Installation for the full extras matrix.
For HTTP/SSE (team or remote setup):
Explore further
Setup
Register the server in Claude Code, Cursor, or Codex.
Transports & auth
stdio vs. HTTP/SSE, and securing the HTTP transport with a bearer token.
Default tools
The ten tools visible without
VOICEGW_MCP_ADMIN.Admin tools
Provider config, registration, and delete tools.