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 | Lucid MCPShortlist candidate | Playwright MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Lucid · Publisher source ↗ | First-party MCP Microsoft · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 18, 2026 Package: Sep 21, 2026 |
| Popularity evidence | ||
| GitHub stars | Not documented | 37,525 GitHub stars · checked 2026-09-24T04:14:16.452000Z |
| Package downloads / 30 days | No reliable download data | 23,800,747 package downloads / 30 days · checked 2026-09-24T04:17:39.045000Z |
| Shared repository stars | 3 Shared repository stars (not MCP-specific) · checked 2026-10-20 | 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 | OAuth by default; Lucid Team and Enterprise users can also authenticate with an API key. | The server itself does not require a service account for local stdio use, but websites opened in the controlled browser may use cookies or other authenticated browser state. |
| Cost | No separate MCP fee is documented. Lucid offers free and paid plans; account/product capabilities depend on the selected plan. | The first-party open-source package lists no MCP server usage fee. Normal internet, hosted-client, proxy, or third-party website costs can still apply. |
| Permissions | The MCP can access only documents the authenticated user already has permission to access within the Lucid account; it cannot access documents owned by users outside that account. | The exposed tools can navigate pages, interact with elements, enter text, upload files, inspect network activity, and optionally use additional browser capabilities. |
| Data handling | Lucid states that its MCP server acts as a pass-through and does not retain document content, user prompts, or queries. User credentials are not shared outside the Lucid account. | Page text, accessibility snapshots, console output, network details, uploaded paths, and browser state may be returned to the connected MCP client. Isolated mode keeps the temporary profile in memory; persistent mode stores browser state on disk. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can expose and operate on diagrams/documents the user can access. The main risk is unintended disclosure or modification of collaborative Lucid content within the user's existing permissions. | Playwright MCP is not a security boundary. Secret replacement or masking is a convenience feature, not a security boundary. Prefer an isolated browser profile, non-sensitive test accounts, narrow destinations, minimal optional permissions, and client-side approval controls. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →