voicegw mcp
Start the VoiceGateway MCP (Model Context Protocol) server.Purpose
Themcp command starts an MCP server that exposes 17 tools for AI coding agents to inspect and manage the gateway. Agents like Claude Code, Cursor, and Codex can use these tools to check provider status, view costs, register models, create projects, and more — all without leaving their workflow.
Syntax
Options
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--transport | -t | string | stdio | Transport layer: stdio for local agents, http for remote/SSE. |
--host | string | 127.0.0.1 | HTTP bind host (only used with --transport http). | |
--port | -p | integer | 8090 | HTTP bind port (only used with --transport http). |
--config | -c | string | null | Path to voicegw.yaml. Auto-discovered if omitted. |
Prerequisites
Themcp extra must be installed:
dashboard extra is also needed (for uvicorn and starlette):
Transport Modes
stdio (default)
Used by local coding agents that launch the MCP server as a subprocess. The agent communicates over stdin/stdout using the MCP protocol.HTTP/SSE
Used for remote access or shared team gateways. The server exposes an SSE endpoint at/sse and accepts messages at /messages/.
VOICEGW_MCP_TOKEN environment variable. See MCP Authentication for details.
Examples
Start with stdio for Claude Code
Start HTTP server for remote agents
Start on a custom host and port
Use a specific config file
Available Tools
The MCP server exposes 17 tools across four categories:| Category | Tools |
|---|---|
| Observability | get_health, get_provider_status, get_costs, get_latency_stats, get_logs |
| Providers | list_providers, get_provider, test_provider, add_provider, delete_provider |
| Models | list_models, register_model, delete_model |
| Projects | list_projects, get_project, create_project, delete_project |
Related Commands
voicegw serve— the HTTP API (MCP is a separate server)voicegw dashboard— the web UIvoicegw status— quick status check before starting MCP