Ext Ops Panel
Open dashboard
Comparison

ElevenLabs vs Wixzel Voice

ElevenLabs is an MCP server published by elevenlabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Wixzel Voice is an MCP server published by wixzel.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceElevenLabsWixzel Voice
Docker MCP Catalog Listed
Version: sha256:ad57886f6a7b
Forks (GitHub): 264
Pulls (Docker Hub): 52 137
Stars (Docker Hub): 7
Stars (GitHub): 1 548
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.0
Downloads/month (npm): 359
Downloads/week (npm): 57
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ElevenLabs vs Wixzel Voice
FactElevenLabsWixzel Voice
Marketplaces that list it11
Stars (GitHub) (differs)1 548 (better)0 (worse)
Pulls (Docker Hub) (differs)52 137No figure on Docker Hub
Forks (GitHub) (differs)264 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/elevenlabs)Remote server (mcp.voice.wixzel.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)27Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/elevenlabs/elevenlabs-mcpgithub.com/aqeelshamz/wixzel-voice-sdks
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-02
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 46 h ago returned HTTP 401

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ElevenLabs

In its own words, on Docker MCP Catalog:

Official ElevenLabs Model Context Protocol (MCP) server that enables interaction with powerful Text to Speech and audio processing APIs.

Wixzel Voice

In its own words, on Official MCP Registry:

Lets Claude, Cursor or any MCP client build voice agents and place real phone calls.

How to run each

ElevenLabs As a local MCP server: Docker image

Claude Code
claude mcp add --env "ELEVENLABS_API_KEY=<YOUR_ELEVENLABS_API_KEY>" --transport stdio elevenlabs -- docker run -i --rm -e ELEVENLABS_API_KEY mcp/elevenlabs

Requires: ELEVENLABS_API_KEY (secret)

Wixzel Voice As a remote MCP server

Claude Code
claude mcp add --transport http voice https://mcp.voice.wixzel.com/mcp

Requires: WIXZEL_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Wixzel Voice has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Wixzel Voice publish no list of tools, so we do not compare tools.

Settings each asks for

Only ElevenLabs asks for

  • ELEVENLABS_API_KEY (secret)

Only Wixzel Voice asks for

  • WIXZEL_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: ElevenLabs · What it can do: Wixzel Voice · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built