Data as of

ElevenLabs MCP for Cursor: Setup & Config

Cursor: ElevenLabs MCP brings the vendor's speech and audio services into assistant workflows.

What you can do with ElevenLabs in Cursor

Use the official audio integration when resource delivery matters as much as generating the audio.

  • Work with transcription and speaker distinctions from recorded speech.
  • Deliver generated audio to an MCP client that cannot read the server's local files.

Before you start: ElevenLabs in Cursor

  • uv installed so the client can invoke uvx
  • ElevenLabs account credential
  • Credits available for ElevenLabs operations
  • Assistant or editor with MCP support

The launch matches the Claude Desktop quickstart. Only the API key is needed from this environment list for the basic example; the other entries describe documented options. Windows setup calls for Claude Desktop Developer Mode. If uvx cannot be found, the troubleshooting section suggests configuring its absolute executable path.

ElevenLabs Cursor configuration

  1. Choose Cursor configuration scope

    For ElevenLabs MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add ElevenLabs MCP to Cursor

    Use the elevenlabs-mcp entry below in mcpServers. Keep ElevenLabs MCP's documented stdio connection fields and your other Cursor entries.

  3. Check ElevenLabs MCP in Cursor

    ElevenLabs MCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "elevenlabs-mcp": {
      "command": "uvx",
      "args": [
        "elevenlabs-mcp"
      ],
      "env": {
        "ELEVENLABS_API_KEY": "<credential from your ElevenLabs account>",
        "ELEVENLABS_MCP_BASE_PATH": "<optional root used when resolving relative file paths>",
        "ELEVENLABS_MCP_OUTPUT_MODE": "<optional delivery mode: files, resources, or both>",
        "ELEVENLABS_API_RESIDENCY": "<optional region for enterprise data residency>"
      }
    }
  }
}

Troubleshooting ElevenLabs in Cursor

  • Cursor must find uvx elevenlabs-mcp (from uv, for Python tools) for ElevenLabs MCP. Enable the project/user entry in MCP settings and inspect its tools.
  • Review ELEVENLABS_API_KEY, ELEVENLABS_API_RESIDENCY, ELEVENLABS_MCP_BASE_PATH, ELEVENLABS_MCP_OUTPUT_MODE for ElevenLabs MCP before sharing project .cursor/mcp.json; project scope travels with the repository.
  • ElevenLabs MCP uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Calling the audio capabilities depends on an API credential and available ElevenLabs credits.
  • Known limitation: Regional data residency is restricted to enterprise use.
  • Known limitation: Some lengthy requests can exceed development-inspector time limits.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

ElevenLabs MCP — details. Cursor guide

Frequently asked questions

Cursor's ElevenLabs MCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's elevenlabs-mcp example uses stdio.

ElevenLabs MCP's Cursor configuration invokes uvx elevenlabs-mcp (from uv, for Python tools).

Cursor's ElevenLabs MCP example references ELEVENLABS_API_KEY, ELEVENLABS_API_RESIDENCY, ELEVENLABS_MCP_BASE_PATH, ELEVENLABS_MCP_OUTPUT_MODE. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

No. The README explicitly warns that using these operations needs ElevenLabs credits, in addition to the API key used for access.

Not stated in the README. Only capability summaries and sample requests are supplied, so individual identifiers cannot be listed.