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.

DimensionPuppeteer MCP ServerHeadless browser control & screenshotsFSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS62 / 100 · C66 / 100 · C
Reliability14 / 2010 / 20
Security and permissions11 / 2014 / 20
Maintenance10 / 2015 / 20
Documentation14 / 2015 / 20
Setup experience13 / 2012 / 20
Best for
  • Testing and collection tasks that need an assistant to inspect rendered pages
  • Development teams automating screenshots, form filling, or browser regression checks
  • 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
  • Environments that prohibit automated external browsing or web-account credentials
  • Production-scale scraping that requires advanced anti-bot handling and distributed execution
  • 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
  • Permission to launch a local Chromium process
  • Network access to target websites and, for authenticated flows, a suitable test account
  • 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
  • Automated clicks and form fills can trigger real submissions or external side effects
  • Screenshots, page content, and browser sessions may expose sensitive information
  • 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, Cursor, ClineClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools530