Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldElevenLabs MCPShortlist candidateChrome DevTools MCPMCP100 Recommended
Task fit
Best for
  • Managing ElevenLabs voice and chat agents from an MCP client
  • Creating, updating, duplicating, testing, and inspecting agent configurations
  • Generating speech and other supported creative media with explicit user intent
  • Working with ElevenLabs knowledge bases, tests, deployments, and conversation diagnostics
  • Inspecting pages, console and network activity, automating browser actions, and collecting performance evidence in Chrome
Not ideal for
  • Local-only or offline workflows
  • Users who cannot authorize an external AI client to access an ElevenLabs workspace
  • Workflows that require a stable, credential-free, universally identical tool surface
  • API-only testing or browsers outside the project's documented Chrome support
Avoid when
  • The assistant must not be able to modify or delete ElevenLabs workspace resources
  • Creative generation spend cannot be supervised
  • Workspace or conversation data cannot be sent through a hosted third-party service
  • The controlled browser contains personal accounts, secrets, or sessions that the MCP client must not inspect or modify
Provenance
Provenance details

First-party MCP

endpoint:https: · Publisher source ↗

Community implementation

io.github.ChromeDevTools · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 22, 2026

Package: Aug 22, 2026

Repo: Sep 24, 2026

Package: Sep 21, 2026

Popularity evidence
GitHub starsNot documented

52,542

GitHub stars · checked 2026-09-24T04:14:16.273000Z

Package downloads / 30 daysNo reliable download data

7,881,886

package downloads / 30 days · checked 2026-09-24T04:17:39.032000Z

External adoption evidenceNot documented
  • npm: package downloads: 7,541,930Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth sign-in to ElevenLabs; revocable workspace-scoped access; no MCP API key required.No server authentication is documented for local stdio. Running-browser connections support optional WebSocket headers; an open remote-debugging port lets local applications control Chrome.
CostConnecting the MCP does not require a local install or MCP API key. Creative generation and other metered ElevenLabs operations may consume account credits; estimate-first guidance is documented for costly generations.The open-source npm package lists no MCP fee. Chrome, Node.js, client, model, and external-service costs are separate.
PermissionsOAuth-scoped workspace access. Official MCP guidance includes read operations plus create/update/duplicate/delete agent and related resource operations; destructive calls exist.Inspects, debugs, automates, and modifies browser state through navigation, input, script evaluation, screenshots, uploads, extensions, memory, performance, and PWA tools.
Data handlingRemote hosted service. Tool requests and authorized ElevenLabs workspace/media data are processed through ElevenLabs rather than staying local.Browser content is exposed to the connected client. Performance tools send trace URLs to Google CrUX by default, and usage statistics with invocation success, latency, and environment data are enabled by default; broader retention is not documented.
Limitations
Tradeoffs
  • OAuth removes local API-key management and local server maintenance, but the MCP is now a remote hosted dependency.
  • The hosted server expands beyond the old local speech/audio toolset into agent management and creative workflows, so old tool counts and Context estimates are not portable.
  • Some tools can create, modify, or delete workspace resources, and creative generation can consume credits.
  • Deep DevTools access improves debugging, but exposes browser content and state; usage statistics and CrUX URL lookups are enabled by default unless disabled.
Risk contextHosted OAuth reduces secret-handling burden, but the server can perform state-changing and potentially destructive workspace actions and can trigger credit-consuming media generation. Human confirmation should be retained for destructive or paid operations.Can expose sensitive browser sessions and execute arbitrary browser actions or scripts. Use isolated profiles, URL allow/block patterns, restricted file paths, and do not expose remote-debugging ports.
Evidence date
Editorial review2026-09-04T12:00:00.000Z2026-08-11
Candidate evidence2026-09-14T12:00:00.000Z2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →