MCP100 verdict
No longer recommended. Removed: the official local ElevenLabs MCP was deprecated and archived; use the hosted ElevenLabs MCP successor only after reviewing its Watchlist evidence.
MCP100 Assessment
Editorial verdict
Reviewed 2026-09-04T12:00:00.000Z · Next review 2026-10-04
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Official local ElevenLabs MCP deprecated and archived; successor: https://api.elevenlabs.io/v1/mcp
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observation date unavailable · Downloads observation date unavailable
Historical local implementation.
Historical local package; not comparable for active ordering.
Publisher activity observed 2026-09-04T12:00:00.000Z
Current source snapshot
Source relationship: First-party MCP
Reviewed 2026-09-04T12:00:00.000Z · Next review 2026-10-04
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
No sufficient client-specific setup evidence has been stored from the publisher or client documentation.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-09-04T12:00:00.000Z
Loading optional publisher installation details…
No complete evidence-backed client setup steps are currently stored. Optional publisher documentation may provide additional context below.
Capability
Archived local Python MCP retained only as historical provenance for the hosted ElevenLabs successor.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
Related reviewed MCPs
MCP server for Chrome DevTools
Choose this instead if
Choose Chrome DevTools MCP instead if inspecting pages, console and network activity, automating browser actions, and collecting performance evidence in Chrome.
Recommended for browser debugging and performance investigation when Chrome runs with an isolated, non-sensitive profile.
Provide a structured tool for iterative problem-solving steps.
Choose this instead if
Choose Sequential Thinking MCP instead if complex planning and debugging that benefits from revisions and branches.
Provide a structured tool for iterative problem-solving steps.
⚡ Fully automated MCP server + JADX plugin built to communicate with LLM through MCP to analyze Android APKs using LLMs like Claude — uncover vulnerabilities, analyze APK, and reverse engineer effortlessly.
Choose this instead if
Choose JADX-AI-MCP (Part of Zin MCP Suite) instead if navigating JADX decompilation, searching APK code, and accelerating reverse-engineering or security-analysis hypotheses.
Recommended for authorized Android APK triage in an isolated lab, with findings confirmed manually in JADX and the underlying code.
ElevenLabs is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
uv (Python package manager), install with curl -LsSf https://astral.sh/uv/install.sh | sh or see the uv repo for additional install methods.{
"mcpServers": {
"ElevenLabs": {
"command": "uvx",
"args": ["elevenlabs-mcp"],
"env": {
"ELEVENLABS_API_KEY": "<insert-your-api-key-here>"
}
}
}
}
If you're using Windows, you will have to enable "Developer Mode" in Claude Desktop to use the MCP server. Click "Help" in the hamburger menu at the top left and select "Enable Developer Mode".
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
[!WARNING] This local MCP server is deprecated in favor of the ElevenLabs hosted MCP server.
The hosted server is available at
https://api.elevenlabs.io/v1/mcp, with nothing to install or run locally. It authenticates with OAuth, so no API keys are copied into your client. See the hosted MCP server documentation to connect from Claude, Cursor, or any other MCP client.This repository is no longer actively maintained.
For other clients like Cursor and Windsurf, run:
pip install elevenlabs-mcppython -m elevenlabs_mcp --api-key={{PUT_YOUR_API_KEY_HERE}} --print to get the configuration. Paste it into appropriate configuration directory specified by your MCP client.That's it. Your MCP client can now interact with ElevenLabs through these tools:
⚠️ Warning: ElevenLabs credits are needed to use these tools.
Try asking Claude:
You can configure how the MCP server handles file outputs using these environment variables in your claude_desktop_config.json:
ELEVENLABS_MCP_BASE_PATH: Specify the base path for file operations (default: ~/Desktop). This directory is also the security boundary for input files: any path passed to a tool that reads a local file (e.g. speech_to_text, isolate_audio, speech_to_speech, video_to_music, upload_music_for_inpainting) must resolve inside this directory, whether given as an absolute or relative path. Paths outside it — even if absolute and previously accepted — are rejected. Set this to a directory that contains everything you need to read from or write to.ELEVENLABS_MCP_OUTPUT_MODE: Control how generated files are returned (default: files)The ELEVENLABS_MCP_OUTPUT_MODE environment variable supports three modes:
files (default): Save files to disk and return file paths
"env": {
"ELEVENLABS_API_KEY": "your-api-key",
"ELEVENLABS_MCP_OUTPUT_MODE": "files"
}
resources: Return files as MCP resources; binary data is base64-encoded, text is returned as UTF-8 text
"env": {
"ELEVENLABS_API_KEY": "your-api-key",
"ELEVENLABS_MCP_OUTPUT_MODE": "resources"
}
both: Save files to disk AND return as MCP resources
"env": {
"ELEVENLABS_API_KEY": "your-api-key",
"ELEVENLABS_MCP_OUTPUT_MODE": "both"
}
Resource Mode Benefits:
both mode, resources can be fetched later using the elevenlabs://filename URI patternUse Cases:
files: Traditional file-based workflows, local developmentresources: Cloud environments, MCP clients without file system accessboth: Maximum flexibility, caching, and resource sharing scenariosYou can specify the data residency region with the ELEVENLABS_API_RESIDENCY environment variable. Defaults to "us".
Note: Data residency is an enterprise only feature. See the docs for more details.
If you want to contribute or run from source:
git clone https://github.com/elevenlabs/elevenlabs-mcp
cd elevenlabs-mcp
uv venv
source .venv/bin/activate
uv pip install -e ".[dev]"
.env.example to .env and add your ElevenLabs API key:cp .env.example .env
# Edit .env and add your API key
./scripts/test.sh
# Or with options
./scripts/test.sh --verbose --fail-fast
Install the server in Claude Desktop: mcp install elevenlabs_mcp/server.py
Debug and test locally with MCP Inspector: mcp dev elevenlabs_mcp/server.py
Logs when running with Claude Desktop can be found at:
%APPDATA%\Claude\logs\mcp-server-elevenlabs.log~/Library/Logs/Claude/mcp-server-elevenlabs.logCertain ElevenLabs API operations, like voice design and audio isolation, can take a long time to resolve. When using the MCP inspector in dev mode, you might get timeout errors despite the tool completing its intended task.
This shouldn't occur when using a client like Claude.
If you encounter the error "MCP ElevenLabs: spawn uvx ENOENT", confirm its absolute path by running this command in your terminal:
which uvx
Once you obtain the absolute path (e.g., /usr/local/bin/uvx), update your configuration to use that path (e.g., "command": "/usr/local/bin/uvx"). This ensures that the correct executable is referenced.