Chrome Bookmarks MCP

Manage Chrome's synced bookmarks from Claude Code — list, search, add, move, rename, deduplicate, and reorganize whole folder trees. Every edit goes through Chrome's official chrome.bookmarks API, so changes are written into Chrome's own model and sync durably across devices (unlike direct edits to the bookmark file, which the sync engine discards on launch).

How it works

Two coupled components talk over a localhost WebSocket:

Claude Code ──stdio──▶ MCP server ──ws://127.0.0.1:8765──▶ Chrome extension ──▶ chrome.bookmarks
              (this plugin)          (localhost bridge)      (load unpacked)      (synced store)

• MCP server (dist/bundle.cjs) — a stdio MCP server exposing 17 bookmark tools. It starts a localhost WebSocket bridge on port 8765.

• Chrome extension (extension/) — dials into that bridge and runs each operation inside the browser's chrome.bookmarks context.

The MCP server can only act while Chrome is open with the extension loaded; the bookmarks_status tool reports whether the bridge is connected.

Related MCP server: Chrome Bookmark MCP Server

Requirements

• Node.js 18+ (the MCP host runs the bundled server)

• Google Chrome (or a Chromium browser supporting unpacked MV3 extensions)

Install

1. The plugin (MCP server)

From the RedJay marketplace:

/plugin marketplace add JoshuaRamirez/claude-code-plugins
/plugin install chrome-bookmarks-mcp@RedJay

The server is pre-bundled (dist/bundle.cjs) — no npm install needed at plugin-load time.

2. The Chrome extension (one time)

The extension lives in this plugin's extension/ directory. After install, find the plugin root (typically ~/.claude/plugins/cache/RedJay/chrome-bookmarks-mcp/<version>/), then:

1. Open chrome://extensions

2. Turn on Developer mode (top-right)

3. Click Load unpacked and select the plugin's extension/ folder

4. The full bookmark manager opens on first load; re-open any time from the toolbar icon

Not sure which folder to pick? Ask Claude to run bookmarks_status — while disconnected it prints the exact absolute path to load (its extension_dir field). Once loaded and Chrome is running, run it again to confirm the bridge is connected.

Tools

See examples/USAGE.md for a step-by-step walkthrough — first-run check, adding to a folder, safe deduplication, and batch reorganization.

Destructive tools (remove_*, apply_moves) accept a dry_run flag; export first for a backup.

Configuration

If you change the port, update the extension's bridge.js to match.

Troubleshooting

Run bookmarks_status first — when the bridge is disconnected it returns the exact steps to fix it. Common cases:

The extension auto-reconnects (3s retry) if the MCP server restarts, so you rarely need to reload it — just make sure Chrome is running.

Build from source

npm install
npm run build      # esbuild → dist/bundle.cjs
npm test           # smoke + port-conflict suites (no browser needed)
npm run probe      # optional: live connectivity probe (needs the extension)

Contributing? See CONTRIBUTING.md — note that dist/bundle.cjs is committed, so any src/ change must be rebuilt and committed (CI enforces this).

Privacy

No network access beyond the localhost bridge. Bookmarks never leave your machine; the extension talks only to 127.0.0.1.

License

MIT © Joshua Ramirez