Chrome History

Exposes Chrome history data for MCP clients, enabling AI-powered analysis and insights.

other

4

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "vincent-pli-chrome-history-mcp": {
      "command": "uv",
      "args": [
        "run",
        "chrome-history-mcp",
        "--path",
        "/Users/lipeng/Library/Application\\ Support/Google/Chrome/Profile\\ 3/History"
      ]
    }
  }
}

You can run a local MCP server that exposes your Chrome history to AI-powered clients. This enables you to securely share your history data with compatible tools while keeping control over where the data is read from. Use a local MCP runner to start the chrome-history-mcp service and connect your MCP client to fetch insights from your history data.

How to use

To use this MCP server, first start the local process that serves your Chrome history data. You can then connect an MCP client to the running server to query or stream data as needed. The default Chrome history location is automatically used, but you can override it if you maintain multiple Chrome profiles.

How to install

Prerequisites: ensure you have a runtime that can execute the MCP server, such as UV (the MCP runner). You may also need a shell or terminal with permission to run commands.

uv run chrome-history-mcp

This will start the server using the default Chrome history path:

Windows: C:\Users<username>\AppData\Local\Google\Chrome\User Data\Default
macOS: /Users/<username>/Library/Application Support/Google/Chrome/Default
Linux: /home/<username>/.config/google-chrome/Default

If you use a different Chrome profile or a custom history location, specify the path with the --path option. For example:

uv run chrome-history-mcp --path /Users/lipeng/Library/Application\ Support/Google/Chrome/Profile\ 3/History

Note: You can quote or escape spaces in paths to ensure the command runs correctly in your shell.

## Additional notes

The server is designed to be used with an MCP client that can communicate via the MCP protocol. Ensure your client is prepared to receive data from the local stdio-based server, and configure any required connection settings in your client environment.

## Configuration and runtime considerations

Default path handling: if you do not provide --path, the server will attempt to use the standard Chrome history path for your operating system. If you have multiple Chrome profiles, you must point the server to the specific History file for the profile you wish to expose.