Chrome history

Chrome history

Talk with AI about your browser history, get fun ^_^

3
Stars
0
Forks
0
Releases

Overview

The chrome-history-mcp server is an MCP server designed to expose your Chrome browser history to AI applications. It reads the local Chrome history database and serves it via the MCP interface, allowing a conversational AI to reference recent browsing activity. By default, it uses the standard Chrome history location for Windows, macOS, and Linux: - 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 You can override the history path by using the --path option, for example to point to a specific profile: /Users/lipeng/Library/Application Support/Google/Chrome/Profile 3/History. The server is started with uv run chrome-history-mcp and is designed to be used in end-to-end workflows with an MCP client such as mcp-cli-host. The repository provides a sample STDIO server configuration that defines an MCP server named a2a-mcp and shows how to run chrome-history-mcp with a --path argument. A snapshot image is provided to illustrate the setup. This MCP server focuses on enabling AI access to Chrome history data within the bounds of the configured path.

Details

Owner
vincent-pli
Language
Python
License
Apache License 2.0
Updated
2025-12-07

Features

Default Chrome history path support

Automatically uses the standard Chrome history location on Windows, macOS, and Linux (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).

Custom history path via --path

Allows pointing to a specific History file or Chrome profile using the --path option (example: /Users/lipeng/Library/Application Support/Google/Chrome/Profile 3/History).

MCP client integration

Designed to be used with an MCP client such as mcp-cli-host for end-to-end workflows.

STDIO server configuration example

Includes a sample STDIO configuration showing how to expose the server as an MCP server (a2a-mcp) and how to run chrome-history-mcp with a --path argument.

Tags

Chrome historybrowser historyMCP serverAICLIpath configurablecross-platformChrome profile