M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCP Server BrowserBrowser access for MCP clients.Playwright MCP ServerPlaywright-based browser automation MCP server
FMRS46 / 100 · D66 / 100 · C
Reliability8 / 209 / 20
Security and permissions8 / 2011 / 20
Maintenance12 / 2015 / 20
Documentation8 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • MCP clients that need browser automation or browser access
  • Local or remote environments using Chrome, Edge, or Firefox
  • Workflows that connect to a browser through CDP or WebSocket
  • Developers who need browser automation from Claude Desktop, VS Code, and similar clients
  • Users doing web testing and scraping
Not for
  • Users seeking functions from the repository's other MCP servers
  • Deployments requiring explicitly documented authentication or managed cloud hosting
  • Environments that cannot grant an agent browser access
  • Environments requiring strict sandboxing that disallow AI-controlled browsers
  • Claude Desktop users needing HTTP/SSE mode (Claude Desktop currently requires stdio mode)
Required permissions
  • Access to the target browser
  • Permission to read browser screenshots when vision is enabled
  • An environment supporting the DISPLAY variable for browser rendering, when needed
  • Access to the specified CDP or WebSocket endpoint for remote connections
  • Corresponding network, directory, or file access when configuring proxies, output directories, or browser executable paths
  • Runs real browsers (Chromium, Firefox, WebKit) locally
  • Automatically downloads and installs browser binaries on first use
  • Writes log files to ~/playwright-mcp-server.log
  • Binds a local port in HTTP mode (default 8931)
Risks and side effects
  • Browser actions may affect pages and data in the active browser session
  • Screenshots or page snapshots may contain sensitive information
  • Misconfigured proxy, CDP, or WebSocket endpoints may broaden browser access
  • The source does not document authentication configuration, so access control must be assessed separately
  • AI can execute JavaScript in a real browser, potentially accessing and manipulating sensitive web content
  • Automatic browser downloads consume disk space and bandwidth
  • HTTP mode binds to localhost only; exposing it via SSH tunnels still requires caution
Supported clientsClaude Desktop, Claude Code, Cline, Cursor, VS Code
Tools01