Launch Chrome with remote debugging to enable use of Chrome DevTools MCP tools. Required before any other DevTools commands.
MIT
510,326 tools. Updated 2026-09-04 00:41
"MCP server for browser automation via Chrome DevTools" matching MCP tools:
- Attach to an already-running Chrome browser via DevTools Protocol for automation, preserving login state, cookies, and extensions. Enable remote debugging in Chrome first.MIT
- Close the active Chrome debugging instance and disconnect the DevTools MCP server.MIT
- Launch a persistent browser session via Pure CDP Mode to enable subsequent automation steps like navigation, clicking, and text entry. Supports headless, incognito, ad-block, and proxy options.MIT
- Launches a persistent Chrome/Chromium session via CDP for browser automation. Call this first to enable navigation, clicks, and content extraction in subsequent operations.MIT
- Authenticate with Google for Chrome Enterprise Premium MCP server access. Initiates OAuth sign-in and handles redirect URL for completing authorization.Apache 2.0
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.3,288,165Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.3,288,165Apache 2.0
Matching MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.
- Clear cached OAuth credentials to force re-authentication for Chrome Enterprise Premium MCP server calls.Apache 2.0
- Follow step-by-step instructions to authenticate via Playwright MCP and save your browser session for fast API access.MIT
- Save NotebookLM authentication cookies when automated CLI login fails. Provide the cookie header from Chrome DevTools to authenticate the MCP server and enable notebook operations.MIT
- Verify MCP server access to your Chrome session by listing open page titles and URLs, then see if an Avito tab is present.MIT
- Launch a browser profile and get automation endpoints (Puppeteer/Playwright WebSocket, Selenium, debug port) to start driving pages immediately.MIT
- Report the current OAuth credential status and cached scopes for Chrome Enterprise Premium. Use this tool to verify authentication state for the MCP server.Apache 2.0
- Start a new browser or mobile automation session. Supports local, cloud, and external WebDriver endpoints with options for headless, attach mode, and tunneling.MIT
- Checks that the dsh-verify MCP server and its Chromium browser are available and ready to run browser verification tests.MIT
- Retrieve visible text from the current device screen, excluding browser chrome, for content analysis and automation workflows.MIT
- Guides setup and use of agent-browser CLI for automated browser tasks like navigating pages, clicking, and capturing console errors in a real browser.MIT
- List managed Chrome browser profiles for a customer, including OS, platform, and user email.Apache 2.0
- Lists capability bundles grouping local MCP servers by tasks like software, filesystem, automation. Provides an overview of available server groups for easier selection and management.MIT
- Automate website interactions in Chrome by giving an AI agent a task prompt and optional iteration limit.Apache 2.0
- Upload local files to browser file inputs using Chrome DevTools Protocol, bypassing the invisible native file picker that would hang the renderer.MIT