Try Bifrost Enterprise free for 14 days.
Request access
[ STDIO MCP ]

How to Use ElevenLabs MCP Server with Bifrost

Use ElevenLabs’ MCP server for AI audio, speech synthesis, voice workflows, and conversational experiences.

[ MCP SERVER SUMMARY ]

ElevenLabs MCP server summary

ElevenLabs MCP lets AI assistants generate speech, clone voices, transcribe audio, and build conversational agents. Bifrost stores ELEVENLABS_API_KEY once and limits which audio tools can spend credits.

PropertyDetails
CompanyElevenLabs
Connection typeSTDIO
AuthenticationElevenLabs API key
Package or endpointelevenlabs-mcp
CapabilitiesText to speech, Voice cloning, Transcription and audio agents
Official documentationElevenLabs MCP documentation

Before you start

  • uv / uvx
  • ElevenLabs API key

What you can do with ElevenLabs

  • Share voice generation with product teams without distributing API keys
  • Restrict expensive voice-clone tools to a creative virtual key
  • Track credit usage via gateway logs of tool invocations
AudioAI Media

[ HOW TO CONNECT ]

Connect ElevenLabs to Bifrost in three steps

1

Install Bifrost

Start the gateway locally or deploy in your VPC.

npx -y @maximhq/bifrost
2

Add ElevenLabs in MCP Gateway

Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose STDIO. Or register via the API below.

• Official Claude Desktop config uses uvx elevenlabs-mcp with ELEVENLABS_API_KEY.

• Optional ELEVENLABS_MCP_OUTPUT_MODE controls file vs resource returns.

3

Point clients at Bifrost /mcp

Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to ElevenLabs.

{
  "mcpServers": {
    "bifrost": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer vk_your_virtual_key"
      }
    }
  }
}

[ EXAMPLE CONFIG ]

Register ElevenLabs via API

Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.

curl -X POST http://localhost:8080/api/mcp/client \
  -H "Content-Type: application/json" \
  -d '{
    "name": "elevenlabs",
    "connection_type": "stdio",
    "stdio_config": {
      "command": "uvx",
      "args": [
        "elevenlabs-mcp"
      ],
      "env": {
        "ELEVENLABS_API_KEY": "env.ELEVENLABS_API_KEY"
      }
    },
    "tools_to_execute": [
      "*"
    ]
  }'

[ WHY BIFROST ]

Run ElevenLabs through one governed gateway

Access control

Virtual keys, RBAC, and tool allowlists per team or agent.

Cost governance

Attribute MCP tool spend alongside LLM usage in one view.

Observability

Log every tool call with latency, server, and virtual key metadata.

Credential isolation

Upstream secrets stay in the gateway — not on every laptop.

[ FAQ ]

Common questions

What does the ElevenLabs MCP server do?

ElevenLabs exposes text to speech, voice cloning, transcription and audio agents to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.

How does ElevenLabs authenticate when used with Bifrost?

ElevenLabs uses ElevenLabs API key. Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.

Can Claude Desktop, Cursor, or Claude Code use ElevenLabs through Bifrost?

Yes. After registering ElevenLabs in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.

[ MCP GATEWAY ]

One gateway for ElevenLabs and every other MCP server

Bifrost MCP Gateway gives you tool-level access control, audit logs, and up to 92% lower token costs when agents orchestrate multiple tools.