Understand a route
List sessions, inspect connected sources and destinations, check devices, and read the current status.
Model Context Protocol
Ask for a route.
Stay in control.
Connect an MCP client to AudioRouter's local tools. Discover the setup, explain the signal path, and make targeted changes within the permissions you grant.
What MCP can do
Useful actions, in plain language.
MCP is an interface to AudioRouter's backend. It does not receive raw microphone audio.
Plan a change
Ask for an effect, mixer input, or connection. Inspect the intended change before applying it.
Control a session
Play or stop, change a node, manage recording, mute privacy, or inspect operation status.
Connect the local server
One backend. Choose your client.
AudioRouter runs its MCP server as a local stdio process through its installed CLI. It uses the same backend as the app and does not add another audio engine or cloud service.
ChatGPT
Work mode + Secure MCP Tunnel
- Keep AudioRouter on the Windows PC that owns the devices.
- In ChatGPT Plugins, choose Add custom MCP server.
- Choose Secure MCP Tunnel and follow ChatGPT's prompts to connect the local AudioRouter MCP process.
- Enable the plugin in a Work chat and select AudioRouter tools for the task.
- In AudioRouter's MCP tab, authorize the client and begin with observer permissions.
ChatGPT's standard remote connector form expects a remote URL. Secure MCP Tunnel is the local-server path. Write-capable MCP access depends on your ChatGPT plan and workspace settings.
OpenAI connection and tunnel guide ↗Anthropic Cowork
Local desktop plugin
- Use Cowork in the Claude Desktop app on the same PC as AudioRouter.
- Create or install a local plugin/desktop extension whose MCP entry launches the AudioRouter CLI with
mcp serve. - Use the executable path and client setup details shown in AudioRouter's MCP tab. Enroll that client ID in AudioRouter.
- Open a Cowork desktop session, select the local plugin, and begin with read-only access.
Claude's web custom connectors run remotely and cannot reach a local stdio server. Local MCP plugins work in the desktop app. AudioRouter currently provides copy-ready setup for Codex and Claude Code; it does not yet ship a Cowork extension package.
Anthropic local vs. remote connector guide ↗Prepare AudioRouterOpen AudioRouter → MCP. Create a unique client ID, authorize it, and use the generated per-install command/config. MCP client enrollment and the HTTP API token are separate credentials.
Permission first
An assistant gets the access you grant.
The backend enforces the same permission scopes for MCP, CLI, and API clients. Reads, graph edits, device administration, plugin scanning, and recording use distinct scopes.
Ambiguous device names need a choice. An inspection request does not arm a recorder. AudioRouter shares configuration and summarized telemetry with tools; it does not stream raw microphone audio to the model.
Read the headless runbook ↗Make your first connection.
Open the MCP tab for current setup details.