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.
| Evidence field | ElevenLabs local MCP (archived)Removed | Chrome DevTools MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP ElevenLabs · Publisher source ↗ | Community implementation io.github.ChromeDevTools · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Aug 14, 2026 Package: Aug 10, 2026 |
| Popularity evidence | ||
| GitHub stars | Not documented | 49,168 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| Package downloads / 30 days | No reliable download data | 9,818,796 package downloads / 30 days · checked 2026-09-08 |
| External adoption evidence | Not documented |
|
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Historical local API-key authentication; the successor uses OAuth. | 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. |
| Cost | Historical local usage was subject to ElevenLabs account pricing. | The open-source npm package lists no MCP fee. Chrome, Node.js, client, model, and external-service costs are separate. |
| Permissions | The retired local server used an ElevenLabs API key; this historical record is not an active setup recommendation. | Inspects, debugs, automates, and modifies browser state through navigation, input, script evaluation, screenshots, uploads, extensions, memory, performance, and PWA tools. |
| Data handling | Historical local operation sent requested content to ElevenLabs services; current hosted data handling is documented on the successor record. | 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 |
|
|
| Risk context | Do not install the archived local server. Review the hosted successor's current OAuth, workspace, and credit-spend boundaries instead. | 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 review | 2026-09-04T12:00:00.000Z | 2026-08-11 |
| Candidate evidence | 2026-09-04T12:00:00.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →