What is a Chrome MCP server?

A Chrome MCP server is a server that exposes your Chrome browsing history.

How can I tell if Chrome is tracking me?

You can check if Chrome is tracking you by reviewing your browsing history, which is exposed by the Chrome History MCP Server. If you see entries that you did not visit, it may indicate tracking.

What is the MCP server for Google search?

The MCP server for Google search is the Chrome History MCP Server, which exposes your Chrome browsing history.

What is MCP server access?

MCP server access refers to the ability to interact with the Chrome History MCP Server, which exposes your Chrome browsing history.

What exactly does an MCP server do?

An MCP server exposes your Chrome browsing history.

MCP Connector

Access Chrome History for AI Chat

Name: Chrome History MCP Server
Availability: OnlineOnly
Author: Peng Li

Chrome History MCP Server exposes your Chrome browsing history.

Connect

Works with chrome

Peng Li

Own this? Claim it

Maintainer of this project? Claim this page to edit the listing.

Spark score

out of 100

Updated Jul 2025

Fresher alternatives ↓

Version 1.0.0

Models

universal

Add to Favorites

Why it matters

Integrate your Chrome browser history into AI applications. Enable conversational AI to understand and discuss your browsing habits.

Outcomes

What it gets done

Extract data from Chrome browser history.

Provide Chrome history access for AI models.

Enable AI-powered analysis of browsing data.

Support multiple Chrome profiles and cross-platform use.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-chrome-history | bash

Overview

Chrome History MCP Server

This MCP server exposes your Chrome browsing history to AI clients. This MCP server exposes your Chrome browsing history to AI clients.

What it does

This MCP server exposes your Chrome browsing history to AI clients.

To set this up, you can run the server using:

uv run chrome-history-mcp

It will use the default Chrome history path for Windows, macOS, and Linux. If your Chrome history is located in a non-default path, you can specify it with the --path argument:

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

For integration with an MCP client like mcp-cli-host, you can configure the mcpServers in your client's configuration:

{
  "mcpServers": {
    "a2a-mcp": {
      "command": "uv",
      "args": [
        "--project",
        "<location of the repo>",
        "run",
        "chrome-history-mcp",
        "--path",
        "<location of your chrome history>"
      ]
    }
  }
}

Source README

A mcp server expose your Chrome history to AI

Setup & Running

uv run chrome-history-mcp

It will use the default Chrome history path:

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

see the details

otherwise use the --path to define the path of history, for example: /Users/lipeng/Library/Application Support/Google/Chrome/Profile 3/History(if you have multiple user in Chrome)

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

E2E

Leverage mcp-cli-host as mcp client

Set STDIO server config

{
  "mcpServers": {
    "a2a-mcp": {
      "command": "uv",
      "args": [
        "--project",
        "<location of the repo>",
        "run",
        "chrome-history-mcp",
        "--path",
        "<location of your chrome history>"
      ]
    }
  }
}

You can get this:

FAQ

Common questions

Discussion