1. Conduid
  2. Developer Tools
  3. Chrome history
MCP server · Developer Tools

Chrome history

by · github.com/vincent-pli/chrome-history-mcp

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

Unclaimed Apache-2.0 last commit a year ago devtools
InstallView source
49Fair

Scored 7 days ago · breakdown

About Chrome history

Chrome history is an MCP server published by vincent-pli in the Developer Tools category: talk with AI about your browser history, get fun ^_^.

The repository has 10 stars and 4 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/vincent-pli/chrome-history-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Chrome history

Powered by Claude · Grounded in docs

I know everything about Chrome history. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

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: shapshot

README fetched from the repository 5 days ago. The original is authoritative.

Questions

About Chrome history

How do I install Chrome history?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Chrome history safe to use with an AI agent?

Its trust score is 49 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Chrome history still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.