C

Chrome

Control a Chrome browser through the Chrome DevTools Protocol (CDP) from MCP clients for browsing, inspection, and automation workflows.

Google·No reviews yet
Repo Docs
Share:

About

Control a Chrome browser through the Chrome DevTools Protocol (CDP) from MCP clients for browsing, inspection, and automation workflows.

Example tools

Illustrative tool names — the actual tool set is defined by the server at runtime.

list_resources
Enumerate resources exposed by this MCP
get_resource
Fetch a resource by ID
invoke
Invoke the primary action of this MCP

Screenshots

No screenshots yet.

Frequently Asked Questions

Common questions about Chrome.

What does the Chrome MCP enable?
The Chrome MCP allows clients to control a Chrome browser programmatically. It facilitates browsing, inspection, and automation workflows using the Chrome DevTools Protocol (CDP).
How can I install the Chrome MCP with an MCP client?
Installation details depend on your MCP client. Typically, you would add the server's repository URL (https://github.com/lxe/chrome-mcp) as a remote. Follow your client's documentation for connecting to a new MCP server.
Does the Chrome MCP require an API key or other credentials?
No, the Chrome MCP does not require an API key, OAuth, or any other explicit credentials for basic operation. It uses a 'none' authentication type.
What are the common use cases for the Chrome MCP?
Common use cases include automated browser testing, web scraping, performance analysis, and debugging web applications. Any task requiring programmatic control over a web browser can benefit.
What are the key capabilities exposed by the Chrome MCP?
The Chrome MCP exposes the full capabilities of the Chrome DevTools Protocol (CDP). This includes DOM manipulation, network interception, JavaScript execution, and screenshot capture.
What are some limitations or prerequisites for using the Chrome MCP?
A key prerequisite is having a Chrome browser installed on the system where the MCP server is running. The server controls external Chrome instances, so a compatible browser environment is necessary.

Install Chrome

Claude Desktop

Add this to claude_desktop_config.json.

{
  "mcpServers": {
    "chrome": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chrome"
      ]
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json.

{
  "mcpServers": {
    "chrome": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chrome"
      ]
    }
  }
}

VS Code

Add this to your workspace settings.json.

{
  "mcp.servers": {
    "chrome": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chrome"
      ]
    }
  }
}

Reviews

Sign in to leave a review.

No reviews yet. Be the first!

Discussion(0)

Sign in to join the discussion.

No comments yet.