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.FSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS46 / 100 · D66 / 100 · C
Reliability8 / 2010 / 20
Security and permissions8 / 2014 / 20
Maintenance12 / 2015 / 20
Documentation8 / 2015 / 20
Setup experience10 / 2012 / 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 want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction
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
  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)
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
  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths
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
  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks
Supported clientsClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools030