J
JoshuaRamirez/chrome-bookmarks-mcp
MCP server + Chrome extension to manage Chrome's synced bookmarks from Claude Code — list, search, add, move,…
★ 1·更新 2026-11-17
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 1 ★ · JoshuaRamirez/chrome-bookmarks-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-17 · 最近见到 2026-11-20 · 共见到 4 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
JoshuaRamirez/chrome-bookmarks-mcp;我们收录于 2026-11-17;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Chrome Bookmarks MCP
以下摘录自该仓库的 README(片段)
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 and 8 tab 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 (and chrome.tabs /
chrome.tabGroups for the tab tools).
The MCP server can only act while Chrome is open with the extension loaded; the
bookmarks_status tool reports whether the bridge is connected.
## 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.
### Many sessions on one machine: run it once, through shared-mcp
The bridge port (8765) can be held by one process only, and every Claude Code
session starts its own copy of an MCP server. Register the server through
shared-mcp so one long-lived
copy owns the port and the extension's socket, and each session is a thin
client of it:
claude mcp add chrome-bookmarks -s user -e BOOKMARK_WRITES=off -- \
python3 ~/Developer/shared-mcp/shared_mcp.py connect --name chrome-bookmarks \
--env BOOKMARK_WRITES -- "$(command -v node)" /abs/path/to/dist/bundle.cjs
A copy that can't bind the port keeps retrying (every BOOKMARK_BRIDGE_RETRY_MS,
default 2000) and takes it when the holder exits, and a copy exits when its
stdin closes, so an orphaned copy never keeps the port. Test:
test/shared-sessions.mjs (two sessions reading at once).
### 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/ /), 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/ /extension),
or use bookmarks_status for the exact extension_dir. Chrome keeps the
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 and 8 tab 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 (and chrome.tabs /
chrome.tabGroups for the tab tools).
The MCP server can only act while Chrome is open with the extension loaded; the
bookmarks_status tool reports whether the bridge is connected.
## 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.
### Many sessions on one machine: run it once, through shared-mcp
The bridge port (8765) can be held by one process only, and every Claude Code
session starts its own copy of an MCP server. Register the server through
shared-mcp so one long-lived
copy owns the port and the extension's socket, and each session is a thin
client of it:
claude mcp add chrome-bookmarks -s user -e BOOKMARK_WRITES=off -- \
python3 ~/Developer/shared-mcp/shared_mcp.py connect --name chrome-bookmarks \
--env BOOKMARK_WRITES -- "$(command -v node)" /abs/path/to/dist/bundle.cjs
A copy that can't bind the port keeps retrying (every BOOKMARK_BRIDGE_RETRY_MS,
default 2000) and takes it when the holder exits, and a copy exits when its
stdin closes, so an orphaned copy never keeps the port. Test:
test/shared-sessions.mjs (two sessions reading at once).
### 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/ /), 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/ /extension),
or use bookmarks_status for the exact extension_dir. Chrome keeps the
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/joshuaramirez-chrome-bookmarks-mcp/)
- 来源
- github · https://github.com/JoshuaRamirez/chrome-bookmarks-mcp
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。