chrome-history

This MCP server provides tools to analyze Chrome browser history and bookmarks data. It exposes several MCP tools you can invoke via your MCP client (e.g., Claude Desktop): search_history to query the browsing history by keywords, URLs, and optional date ranges; get_recent_browsing to retrieve activity from the recent window (e.g., last 24 hours) with visit details and timestamps; and get_history_stats to obtain statistics about the history database such as date ranges and total entries. The server locates the Chrome profile, reads the SQLite History database in read-only mode, and serves the data to your MCP client through standardized MCP actions. Future features mentioned include bookmarks analysis and data export, but the current capabilities focus on read-only history access and basic analytics.

To use it with Claude Desktop, configure the MCP server entry in your Claude config with the node-based command and the path to the server script, then restart Claude Desktop to begin using the tools. Example tool invocation commands can be constructed as plain natural language prompts like: “Search my browser history for 'github'”, “Show me my Chrome history statistics”, or “Show me what I’ve browsed in the last 24 hours.”

Prerequisites:

• Node.js 16+ with ES module support installed on your system
• npm (comes with Node.js)
• Chrome/Chromium installed (and opened at least once to initialize profile data)

Installation steps:

1. Clone the repository: git clone https://github.com/your-username/chrome-history-mcp-server.git cd chrome-history-mcp-server

2. Install dependencies: npm install

3. Run the MCP server: node src/mcp-server.js

If you prefer running via an alternative environment or packaging, ensure the server script path is correctly referenced in your MCP client configuration (see how_to_use for example configurations).

Notes and tips:

• The server reads Chrome's History database in read-only mode to avoid any risk to data integrity.
• Ensure Chrome has been launched at least once and the profile location is accessible by the server.
• If you encounter database locking issues, make sure Chrome is fully closed when the MCP server starts.
• The current features emphasize history analysis; bookmark analysis and exports are listed as future features.
• If you customize the Chrome profile location, you may need to update the server configuration or environment so it can locate the profile directory automatically.
• This server operates entirely locally and does not make network requests, preserving privacy.
• You can adjust the MCP client configuration to point to the server script path that you run locally (see example in README).