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.

DimensionOpenTabsLet AI call real web APIs through your browser session.FSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS49 / 100 · D66 / 100 · C
Reliability6 / 2010 / 20
Security and permissions10 / 2014 / 20
Maintenance9 / 2015 / 20
Documentation12 / 2015 / 20
Setup experience12 / 2012 / 20
Best for
  • Users who want AI to call web APIs through an already authenticated browser session.
  • Users who want local operation with multiple service plugins through an MCP client.
  • Developers building browser-level workflows or custom plugins.
  • 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 who do not use Chrome or do not want to grant AI access to browser sessions.
  • Use cases requiring a cloud-hosted service or a documented OAuth/API-key setup.
  • Integration evaluations that require an evidenced tool inventory and transport protocol.
  • 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
  • Requires installing and running the Node.js CLI.
  • Requires a Chrome extension to access browser tabs and bridge to the local server.
  • AI uses the permissions of accounts currently authenticated in the browser.
  • Plugin tools are off by default and can be set to Off, Ask, or Auto.
  • The project includes anonymous telemetry with an opt-out option.
  • 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
  • An authenticated browser session may allow AI to perform actions permitted to the corresponding service account.
  • Plugin source should be reviewed before enabling it; permissions reset when a plugin is updated.
  • Auto execution reduces opportunities for manual confirmation.
  • Browser actions, network capture, and third-party service calls may create unintended external effects.
  • 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