Skip to main content
Glama
Chrome Bookmarks MCP

Chrome Bookmarks MCP

Chrome Bookmarks MCP

CI Release License: MIT

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: browser-mcp

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.

After a marketplace or plugin version bump, re-Load unpacked from the new versioned cache path (~/.claude/plugins/cache/RedJay/chrome-bookmarks-mcp/<version>/extension), or use bookmarks_status for the exact extension_dir. Chrome keeps the previously loaded folder and does not follow the old path automatically. Open chrome://extensions, remove the old unpacked extension, Load unpacked from that new folder, then re-run bookmarks_status and confirm extension_version matches server_version.

Tools

Tool

Purpose

bookmarks_status

Is the extension bridge connected?

stats

Count of folders and URLs

list_folders

Every folder with id, depth, and full path

list_bookmarks

Flat list of bookmarks ({id,title,url,folder}), optionally scoped to a folder path

search_bookmarks

Live filter across all bookmarks

add_bookmark

Create a bookmark, targeting any folder or path

create_folder

Create a folder under any parent or path

ensure_folder_path

Idempotently create a nested folder path

update_bookmark

Rename and/or change a bookmark's URL

move_bookmark

Relocate a bookmark or folder

remove_bookmark

Delete a bookmark or folder (optionally recursive)

find_duplicates

Group bookmarks sharing a URL

remove_duplicates

Keep one of each URL, remove the rest

remove_empty_folders

Prune folders with no descendants (supports dry_run)

apply_moves

Batch-move bookmarks from a plan TSV (supports dry_run)

export_json

Export the whole tree as portable JSON

import_json

Recreate an exported JSON tree under a target folder (backup restore)

See examples/USAGE.md for a step-by-step walkthrough — first-run check, adding to a folder, safe deduplication, and batch reorganization. tools/classify.py writes a starter plan TSV for apply_moves; it moves nothing.

remove_duplicates, remove_empty_folders, and apply_moves accept a dry_run flag; remove_bookmark does not. Export first for a backup.

Configuration

Env var

Default

Purpose

BOOKMARK_BRIDGE_PORT

8765

WebSocket port the server listens on / the extension dials

BOOKMARK_PLAN_FILE

~/.chrome-bookmarks-mcp/proposed-moves.tsv

Default plan file for apply_moves

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:

Symptom

Cause

Fix

Tools error with "Chrome bridge not connected"

Extension not loaded, or Chrome is closed

Open Chrome; load the extension unpacked (see step 2 above)

bookmarks_status reports EADDRINUSE / listening: false

Another process (usually a second server) is holding BOOKMARK_BRIDGE_PORT

Free the port, or set BOOKMARK_BRIDGE_PORT to a free port and match BRIDGE_URL in extension/bridge.js

Connected, but extension_version is missing or differs from server_version

Chrome is still running an older unpacked extension from a previous cache path

Remove it at chrome://extensions and Load unpacked from the extension_dir in that status result, then re-run bookmarks_status

Was working, now times out

Chrome was quit, or the MV3 service worker went idle

Re-open Chrome / click the toolbar icon once to wake the worker; the extension re-dials automatically within a few seconds

Still disconnected after loading

Port mismatch

The extension dials ws://127.0.0.1:8765; if you set BOOKMARK_BRIDGE_PORT, edit BRIDGE_URL in extension/bridge.js to match

apply_moves can't find its plan

No plan file at the default path

Pass file_path, or set BOOKMARK_PLAN_FILE

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 + bookmarkstore + apply-moves (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

Available Tools

17 tools
add_bookmarkA

Add a bookmark. Target a folder by folder_path (created if missing, default 'Bookmarks bar') or by parent_id. A folder_path's top level must be 'Bookmarks bar', 'Other bookmarks', or 'Mobile bookmarks'.

Inputs: url (required), title (required), parent_id, folder_path.

apply_movesA

Apply a catalogue plan TSV (columns: id, proposed, current, via, title, url). Creates each target folder and moves the bookmark into it. dry_run=true previews counts without changing anything. delete_junk=true also removes rows whose proposed folder is 'DELETE?'.

Inputs: dry_run, file_path, delete_junk.

bookmarks_statusA

Report whether the Chrome extension bridge is connected and on what port. When disconnected, returns step-by-step setup guidance — call this first if any other tool fails to reach the browser.

Inputs: no named parameters.

create_folderA

Create a folder under parent_path (created if missing, default 'Bookmarks bar') or parent_id. A parent_path's top level must be 'Bookmarks bar', 'Other bookmarks', or 'Mobile bookmarks'.

Inputs: name (required), parent_id, parent_path.

ensure_folder_pathA

Ensure a nested folder path exists (e.g. 'Bookmarks bar/Work/Reports'), creating missing levels. Returns the leaf folder. Top level must be 'Bookmarks bar', 'Other bookmarks', or 'Mobile bookmarks'.

Inputs: path (required).

export_jsonA

Export the whole bookmark tree as portable JSON. If file_path is given, write it server-side and return the path; otherwise return the JSON.

Inputs: file_path.

find_duplicatesB

List groups of bookmarks that share the same URL.

Inputs: no named parameters.

import_jsonA

Import a previously exported bookmark JSON file (see export_json) under a target folder. Recreates the tree; it does NOT deduplicate, so importing into a folder that already has the same bookmarks will create copies. Target via into_path (created if missing, default 'Other bookmarks') or into_parent_id.

Inputs: file_path (required), into_path, into_parent_id.

list_bookmarksA

List bookmarks as a flat array of {id, title, url, folder}. Optionally scope to a folder path (e.g. 'Bookmarks bar/Dev') to avoid returning the whole tree; omit to list everything.

Inputs: folder_path.

list_foldersA

List every folder with its id, title, depth, and full path — useful before adding/moving.

Inputs: no named parameters.

move_bookmarkA

Move a node into a folder by to_path (created if missing) or to_parent_id. A to_path's top level must be 'Bookmarks bar', 'Other bookmarks', or 'Mobile bookmarks'.

Inputs: id (required), to_path, to_parent_id.

remove_bookmarkA

Remove a bookmark by id, or a folder and its contents (set recursive=true for folders).

Inputs: id (required), recursive.

remove_duplicatesA

Remove duplicate-URL bookmarks, keeping the first in each group. Use dry_run=true to preview without deleting.

Inputs: dry_run.

remove_empty_foldersA

Sweep the tree and delete folders that contain no bookmarks (bottom-up), e.g. folders left empty after a re-catalogue. Skips the permanent roots. dry_run=true lists them without deleting.

Inputs: dry_run.

search_bookmarksA

Search bookmarks by text in title or URL.

Inputs: query (required).

statsA

Return counts of bookmarks and folders.

Inputs: no named parameters.

update_bookmarkA

Update a node's title and/or a bookmark's URL, by id.

Inputs: id (required), url, title.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct operation: adding, creating, moving, removing, updating, searching, listing, finding duplicates, exporting/importing, applying batch moves, and checking status. No overlapping purposes.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., add_bookmark, remove_empty_folders), but 'bookmarks_status' and 'stats' deviate slightly from the verb-first convention.

    Tool Count5/5

    17 tools cover all essential bookmark management operations without being excessive. The count is proportional to the domain's complexity.

    Completeness5/5

    The set covers full CRUD, search, duplicate handling, import/export, batch moves, folder management, and connection status. No obvious gaps for typical bookmark workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server implementation that provides seamless integration between Chrome bookmarks and AI assistants. This server enables AI models to access, search, analyze, and manage Chrome bookmarks through a standardized protocol.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unified MCP server for browser automation (Playwright + CDP + CLI) and bookmark management across Chrome, Firefox, Edge, and Brave, including cross-browser sync, deduplication, and a React dashboard.
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to search, browse, add, and delete Chrome and Edge bookmarks through the MCP protocol, using a local FastMCP server that directly reads and modifies browser bookmark files.
      5
      -