MCP Server

Overview#

Menace Voice exposes an MCP (Model Context Protocol) server that lets AI assistants like Codex, Claude Code, Claude Desktop, and Cursor access your workspace and documentation. Once connected, an assistant can list your agents, fetch agent definitions, and search Menace Voice docs on your behalf.

Prerequisites#

• A Menace Voice API key. Generate one at /api-keys (or http://localhost:3010/api-keys for self-hosted). See API Keys.
• Your Menace Voice MCP endpoint:
  • Hosted: https://voice.menaceui.com/api/v1/mcp/
  • Self-hosted: <YOUR_BACKEND_URL>/api/v1/mcp/

The endpoint is also shown in Platform Settings → MCP Server inside the Menace Voice UI.

Claude Code#

Register Menace Voice as an MCP server with the Claude Code CLI:

claude mcp add --transport http menace-voice https://voice.menaceui.com/api/v1/mcp/ \  --header "X-API-Key: YOUR_API_KEY"

Replace YOUR_API_KEY with the key you generated. For self-hosted deployments, swap the URL for your backend.

Verify the server is connected:

claude mcp list

Codex#

Open Codex's config file (~/.codex/config.toml) and add a menace-voice MCP server:

[mcp_servers.menace-voice]url = "https://voice.menaceui.com/api/v1/mcp/"http_headers = { "X-API-Key" = "YOUR_API_KEY" }

Replace YOUR_API_KEY with the key you generated. For self-hosted deployments, replace the URL with your backend MCP endpoint.

If you prefer to keep the API key out of config.toml, store it in an environment variable instead:

[mcp_servers.menace-voice]url = "https://voice.menaceui.com/api/v1/mcp/"env_http_headers = { "X-API-Key" = "MENACE_VOICE_API_KEY" }

Then set the API key before starting Codex:

export MENACE_VOICE_API_KEY="YOUR_API_KEY"codex

Verify the server is registered:

codex mcp listcodex mcp get menace-voice

Claude Desktop#

Open Claude Desktop's config file (claude_desktop_config.json) and add the menace-voice entry under mcpServers:

{  "mcpServers": {    "menace-voice": {      "url": "https://voice.menaceui.com/api/v1/mcp/",      "headers": {        "X-API-Key": "YOUR_API_KEY"      }    }  }}

Restart Claude Desktop after saving. The Menace Voice tools should appear in the tool picker.

Cursor and other MCP clients#

Any MCP client that supports Streamable HTTP transport can connect with the same URL and header. Paste the configuration above into your client's MCP settings file and replace YOUR_API_KEY.

Example prompts#

Once the MCP server is connected, you can drive Menace Voice from your coding agent in plain English. A few prompts to try:

Explore your workspace

• "List my agents in Menace Voice."
• "Show me the definition of the agent called Lead Qualifier."
• "Which credentials and tools are configured in my Menace Voice workspace?"
• "List the recordings from my most recent agent."

Edit an agent

• "In my Lead Qualifier agent, add a new agent node after the greeting that asks the caller for their budget, then routes to the existing qualification node."
• "Add an end-call node to Support Bot that triggers when the user says they are done, with a polite goodbye prompt."
• "Rename the intro node in Lead Qualifier to greeting and update any edges that reference it."
• "Change the LLM model on all agent nodes in Support Bot to gpt-4o-mini."

Learn the platform

• "Search the Menace Voice docs for how to configure a TURN server."
• "What node types does Menace Voice support, and what fields does a knowledge_base node take?"
• "How do I deploy Menace Voice on a custom domain with HTTPS?"