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 | Runway API MCP ServerWatchlist candidate | Chrome DevTools MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP ecosystem:runway-api · Publisher source ↗ | Community implementation io.github.ChromeDevTools · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 10, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 10, 2026 |
| Popularity evidence | ||
| GitHub stars | 22 GitHub stars · checked 2026-08-14T18:46:26.000Z | 49,168 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | No reliable download data | 7,541,930 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP | 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 | The official server uses a Runway API key. | 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 | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. | The open-source npm package lists no MCP fee. Chrome, Node.js, client, model, and external-service costs are separate. |
| Permissions | Runway API credentials, model access, content policy, and account quotas govern generation. | Inspects, debugs, automates, and modifies browser state through navigation, input, script evaluation, screenshots, uploads, extensions, memory, performance, and PWA tools. |
| Data handling | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive ai & reasoning information. | 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 | The repository has a short history, no strong release track record, and requires source-based setup. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. | 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-07-30 | 2026-08-11 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →