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.

DimensionNotebookLM MCP ServerDrive NotebookLM via a real Chrome browser, bringing citation-backed answers to your AI agents.Chrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS55 / 100 · C76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions10 / 2012 / 20
Maintenance9 / 2017 / 20
Documentation17 / 2017 / 20
Setup experience13 / 2017 / 20
Best for
  • Power users needing reliable answers based on user-uploaded documents with reduced hallucinations.
  • Developers already using Claude Code, Cursor, or Codex who want to extend capabilities with NotebookLM.
  • Workflows that automate extensive document research or content generation.
  • Frontend developers who want AI-assisted web debugging and performance analysis
  • Scenarios that need browser automation and performance diagnostics in the same tool
Not for
  • Users without a Google account or NotebookLM access.
  • Users who cannot run Chrome or headless servers without xvfb (WSL1 is not supported).
  • Those needing a lightweight, browserless solution (this server depends on a real Chrome).
  • Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
Required permissions
  • Requires Google account login to access NotebookLM service.
  • Requires running Chrome/Chromium via Patchright, and may modify its profile files.
  • Can read/write local filesystem to store Chrome profiles, library data, and audio files.
  • May listen on local ports (default 3000 in HTTP mode) to serve MCP.
  • May make network requests to NotebookLM and Google services.
  • Requires a local Chrome browser instance to run
  • navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
Risks and side effects
  • Browser automation may trigger Google's anti-automation detection, potentially leading to account restrictions.
  • Chrome profile stores login credentials without encryption, posing credential leak risk.
  • Third-party source content may contain malicious instructions; AI marker and disclaimers mitigate but cannot eliminate risk.
  • Long-running sessions may accumulate browser sessions; monitor session timeouts and resource usage.
  • Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
  • performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
Supported clientsClaude Code, Cursor, Codex, Generic MCP client, HTTP-only clientsClaude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity
Tools1922