chrome-bookmarks-mcp
You can inspect and modify Chrome bookmarks through an MCP client by relaying commands to the companion Chrome extension.
Check whether the Chrome extension is connected.
Browse the bookmark tree/subtree, list folder children, fetch nodes by ID, search bookmarks, and list recently added bookmarks.
Create bookmarks or folders, update titles/URLs, and move/reorder nodes.
Remove single bookmarks/empty folders or recursively remove folder trees; destructive operations are annotated for confirmation.
Request read results as human-readable text or raw JSON
BookmarkTreeNodedata.
Allows reading and writing Chrome bookmarks, including managing bookmark folders, searching, creating, updating, moving, and removing bookmarks through Chrome's bookmark API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@chrome-bookmarks-mcp list my bookmark folders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
chrome-bookmarks-mcp
An MCP server that lets Claude Code (or any MCP client) read and write your Chrome bookmarks, using a small companion Chrome extension.
MCP client ──(stdio / MCP)── chrome-bookmarks-mcp ──(WebSocket 127.0.0.1:17870-17874)── extension ──(chrome.bookmarks)── ChromeChrome exposes bookmark editing only to extensions (chrome.bookmarks), and editing the Bookmarks file directly does not work while Chrome is running. So this project ships two parts:
chrome-bookmarks-mcp(npm) — the MCP server. It starts a WebSocket listener on127.0.0.1and forwards tool calls to the extension.Chrome Bookmarks MCP Bridge (
extension/) — a Manifest V3 extension that connects to the server and executeschrome.bookmarkscalls on its behalf.
Features
A
chrome-bookmarksCLI for use without a resident MCP server (see CLI)11 tools: status, get_tree, get_children, get, search, get_recent, create, update, move, remove, remove_tree
Multiple MCP clients at once: the server takes the first free port in 17870–17874, the extension connects to all five
Local only: the server binds to
127.0.0.1and accepts connections whoseOriginischrome-extension://The extension runs only a fixed whitelist of
chrome.bookmarksAPIsDestructive tools (
remove,remove_tree) are annotated withdestructiveHintso clients can ask for confirmation
Related MCP server: Chrome Bookmarks MCP
Setup
Requires Node.js 18+ and Google Chrome (or another Chromium browser that supports MV3 extensions).
1. Register the MCP server
Claude Code:
claude mcp add --scope user chrome-bookmarks -- npx -y chrome-bookmarks-mcp
claude mcp list # chrome-bookmarks: ✔ ConnectedAny other MCP client — add to its server configuration:
{
"mcpServers": {
"chrome-bookmarks": {
"command": "npx",
"args": ["-y", "chrome-bookmarks-mcp"]
}
}
}2. Load the extension (once per Chrome profile)
Download
chrome-bookmarks-mcp-extension-<version>.zipfrom the Releases page and unzip it (or use theextension/folder of this repository).Open
chrome://extensionsand turn on Developer mode (top right).Click Load unpacked and select the unzipped folder.
A green bookmark icon appears in the toolbar. Its badge shows the number of connected MCP servers (empty while no MCP client is running).
Load it in the profile whose bookmarks you want to edit. If the extension is loaded in several profiles, the server sends commands to the most recently connected one.
Chrome shows a "Disable developer mode extensions" prompt on startup for unpacked extensions. Dismiss it (or click "Cancel"); the extension keeps working.
3. Try it
Open a new Claude Code session and ask, for example, "list my bookmark folders". Claude will call bookmarks_get_tree.
Tools
Tool | Description |
| Connection status with the extension (check this first when something fails) |
| Whole tree or subtree under an id, as |
| Direct children of a folder, in order |
| Nodes by id |
| Free-text search (Chrome's built-in) or exact title / url match |
| Recently added bookmarks |
| Create a bookmark or a folder (omit |
| Change title / URL |
| Move to another folder or reorder |
| Remove one bookmark or an empty folder |
| Remove a folder with everything inside |
Every read tool accepts format: "json" to get the raw BookmarkTreeNode objects instead of the text listing.
The ids of the top-level folders (Bookmarks bar / Other bookmarks / Mobile bookmarks) differ between Chrome profiles. Call bookmarks_get_children with id 0 to look them up.
CLI (no resident MCP server)
The package also installs a chrome-bookmarks command. It needs no MCP registration, so nothing runs while you are not using it. This suits clients that can run shell commands (such as Claude Code through a skill) and setups with many parallel sessions, where one MCP server per session adds up.
npm install -g chrome-bookmarks-mcp
chrome-bookmarks children 0 # top-level folders
chrome-bookmarks search "anthropic"
chrome-bookmarks create --parent 1 --title "Docs" --url https://docs.claude.com/
chrome-bookmarks help # all commandsCommand | Same as |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Start the daemon and return at once, so the extension connects in the background (warm-up) |
| Stop the background daemon |
Add --json to print the raw BookmarkTreeNode data.
How it works: the first command starts one shared background daemon on a free port in 17870–17874 and waits for the extension. The extension reconnects every 30 s, so the first command can take up to ~30 s; later commands reuse the connection and return at once. The daemon exits by itself after 10 minutes without commands (CHROME_BOOKMARKS_IDLE_MS changes this). It writes its port and a random token to <temp>/chrome-bookmarks-mcp/daemon-<ports>.json, and its log to daemon.log in the same folder. The MCP server and the CLI can be used side by side.
Troubleshooting
Symptom | What to check |
"Chrome extension is not connected" | Is Chrome running? Is the extension enabled at |
| Run |
The extension's Errors list fills with | Harmless, and fixed in extension 0.1.1: older versions tried every port every 30 s and each port without a server logged a failure. Update the extension, then clear the list. |
Bookmarks of the wrong profile are changed | The server talks to the most recently connected extension. Disable the extension in profiles you do not want to edit. |
Development
git clone https://github.com/masaodev/chrome-bookmarks-mcp.git
cd chrome-bookmarks-mcp
npm install
npm test # smoke test with a fake extension (no Chrome needed)
npm run live # read-only check against the real extension (load extension/ first)
npm run pack:extension # dist/chrome-bookmarks-mcp-extension-<version>.zipTo run the server from a checkout instead of npm:
claude mcp add --scope user chrome-bookmarks -- node /path/to/chrome-bookmarks-mcp/server/index.jsDesign notes
MV3 service workers are suspended after ~30 s of inactivity, so the server sends an application-level ping every 20 s and the extension also reconnects from a 30 s alarm.
A failed WebSocket connection is always logged as an extension error, so the extension first probes each port with a quiet
fetch(the server answers plain HTTP with 426) and opens a WebSocket only where a server is listening.Native Messaging was not used: the host Chrome would spawn and the MCP server the client spawns are separate processes, so a bridge would be needed anyway. One WebSocket does the job.
CHROME_BOOKMARKS_MCP_PORTS=17879,17878(comma-separated) overrides the candidate ports. The smoke test uses this so that a test server never shares the 17870–17874 range with real sessions or the real extension.The server and the extension share a tiny JSON protocol (
{id, api, args}→{id, result | error}), so keep their versions in step.
Security
The server listens on the loopback interface only and rejects connections without a chrome-extension:// origin. The extension only executes the whitelisted chrome.bookmarks methods listed in background.js. Any local process could in principle connect to the port and pose as an MCP server; if that matters in your environment, disable the extension when not in use.
The CLI daemon only accepts commands that carry the random token from its state file and no Origin header, so web pages cannot drive it.
License
Available Tools
11 toolsbookmarks_createCreateA
Create a bookmark or a folder. Omit url to create a folder. If parentId is omitted, Chrome puts it in "Other bookmarks".
Inputs: title (required), url, index, parentId.
bookmarks_getGet by idBRead-only
Return the nodes with the given ids.
Inputs: ids (required), format.
bookmarks_get_childrenGet childrenARead-only
Return the direct children (folders and bookmarks) of a folder, in display order.
Inputs: id (required), format.
bookmarks_get_recentRecently addedBRead-only
Return recently added bookmarks, newest first.
Inputs: count, format.
bookmarks_get_treeGet treeARead-only
Return the whole bookmark tree (or the subtree under id). Use it to find folder ids. The ids of the top-level folders (Bookmarks bar / Other bookmarks) differ per Chrome profile, so call bookmarks_get_children with id 0 to look them up.
Inputs: id, format.
bookmarks_moveMoveA
Move a node to another folder, or reorder it within the same folder.
Inputs: id (required), index, parentId.
bookmarks_removeRemove (single)ADestructive
Remove one bookmark or an empty folder. For a non-empty folder use bookmarks_remove_tree. This cannot be undone; confirm the target with the user before calling.
Inputs: id (required).
bookmarks_remove_treeRemove folder recursivelyADestructive
Remove a folder and everything inside it. This cannot be undone; inspect the subtree with bookmarks_get_tree and get the user's approval before calling.
Inputs: id (required).
bookmarks_searchSearchARead-only
Search bookmarks. query = word match against title and URL (Chrome's built-in search). title / url = exact match.
Inputs: url, query, title, format.
bookmarks_statusConnection statusARead-only
Return the connection status with the Chrome extension. Check this first when a bookmark operation fails.
Inputs: no named parameters.
bookmarks_updateUpdateB
Change the title and/or URL (only the fields given).
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
Scored across 11 tools
Each tool targets a distinct operation: status, tree navigation, search, retrieval, create, update, move, and removal (single vs. tree). The overlap between get_tree, get_children, and get is clearly delineated by their descriptions.
All tools follow a uniform bookmarks_<verb> pattern, with verbs like get_tree, get_children, search, create, update, move, remove, and remove_tree. This makes the API predictable and easy to navigate.
11 tools is well-scoped for a bookmark management server. Each tool covers a necessary part of the lifecycle without redundancy or bloat.
The surface covers the full bookmark lifecycle: create, read (tree/children/get/search/recent), update, move, and delete (single and tree). The status tool handles connectivity, leaving no obvious gaps for typical bookmark operations.
Maintenance
Related MCP Connectors
reMarkable MCP server for ChatGPT, Claude and any AI agent: list files and folders, import PDF or EPUB, rename file, move file to folder, move file to trash and read subscription and payment history in your own reMarkable account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to reMarkable yourself; Cotlet does not store your password and you need no reMarkable API key. About the official reMarkable API: reMarkable has no public API and no official MCP server for its cloud (checked 25 Oct 2026). Files move through the desktop and mobile apps, the Import button at my.remarkable.com, the Read on reMarkable browser extension and Office add-ins, and the Google Drive, Dropbox and OneDrive integrations on the tablet. Setup and FAQ: https://cotlet.dev/integrations/remarkable-api-mcp-server
Recall MCP server for ChatGPT, Claude and any AI agent: save URL, create note, add tags to card, remove tags from card, delete card, export card as Markdown, search cards and list card connections in your own Recall account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Recall yourself; Cotlet does not store your password and you need no Recall API key. About the official Recall API: Yes, but it only reads. Recall has a REST API and an MCP server, both included in the Free plan, and both are read-only (checked 25 Oct 2026). Setup and FAQ: https://cotlet.dev/integrations/recall-api-mcp-server
Plex MCP server for ChatGPT, Claude and any AI agent: search libraries, list library items, add to Watchlist, mark item watched, add to playlist, list collections, grant library access and revoke library access in your own Plex account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Plex yourself; Cotlet does not store your password and you need no Plex API key. About the official Plex API: Plex has a documented HTTP API for Plex Media Server and no official MCP server (checked 5 Nov 2026). The API covers libraries, playlists, collections and playback history on one server and needs an X-Plex-Token. Setup and FAQ: https://cotlet.dev/integrations/plex-api-mcp-server
Zotero MCP server for ChatGPT, Claude and any AI agent: add item by DOI, search library, add to collection, get annotations, create note and export citations in your own Zotero account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Zotero yourself; Cotlet does not store your password and you need no Zotero API key. About the official Zotero API: Zotero has a public Web API v3 with read and write access (checked 16 Oct 2026). You create a key in your zotero.org account settings and send it with each request. Setup and FAQ: https://cotlet.dev/integrations/zotero-api-mcp-server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA 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.3MIT
- AlicenseAqualityBmaintenanceManages Chrome's synced bookmarks through an MCP server and Chrome extension, enabling operations like listing, searching, adding, moving, and deduplicating bookmarks.171MIT
- FlicenseAqualityCmaintenanceEnables 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-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives Claude read/write access to Chrome bookmarks for agentic reorganization, including tree analysis, folder proposals, batch operations with snapshots, deduplication, and dead-link detection.1MIT