Chromedp MCP Server

Connect Chromedp MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server that provides browser automation capabilities using chromedp. This server enables AI assistants to interact with web pages, manage browser instances, and perform various web automation tasks. The chromedp mcp mcp server is what makes that connection.

What the server does

• Multi-instance Chrome Management — Create and manage multiple Chrome browser instances with extensive configuration options (headless mode, security settings, performance optimization)
• Complete Page Navigation — Navigate to URLs, browser history navigation (back/forward)
• Element Interaction — Find, click, and interact with web page elements using various selectors
• Form Operations — Input text, set values directly
• Cookie Management — Set and manage browser cookies for session handling
• File Operations — Download files and images from web pages

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Other — The Other tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: CHROME_MAXIMUM_INSTANCE, CHROME_TTL, CHROME_EXE_TIMEOUT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Chrome/Chromium Browser: Must be installed and accessible in system PATH - Go: Version 1.19 or higher for building from source

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Chromedp MCP's toolset — Other — is a fair guide to whether it matches your workflow. It is maintained by KePatrick; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.