ElevenLabs vs Screenify Studio
ElevenLabs is an MCP server published by elevenlabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Screenify Studio is an MCP server published by screenify.studio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ad57886f6a7b Forks (GitHub): 257 Pulls (Docker Hub): 50 557 Stars (Docker Hub): 7 Stars (GitHub): 1 535 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.1 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
| Fact | ElevenLabs | Screenify Studio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 535 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 50 557 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 257 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/elevenlabs) | On your machine (https://github.com/ScreenifyStudio/screenify-mcp/releases/download/v2.2.1/screenify.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 27 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/elevenlabs/elevenlabs-mcp | github.com/screenifystudio/screenify-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Official ElevenLabs Model Context Protocol (MCP) server that enables interaction with powerful Text to Speech and audio processing APIs.
Screenify Studio
Record your screen and export studio-styled demo videos on macOS, driven by your AI assistant.
How to run each
ElevenLabs As a local MCP server: Docker image
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)
Screenify Studio
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Screenify Studio publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Screenify Studio publish no settings it asks for, so we do not compare settings.
What it can do: ElevenLabs · What it can do: Screenify Studio · 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.