Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Read-only MCP server for browser bookmarks: Chrome, Safari, Firefox, and read-later exports.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"bookmarks": {
"command": "npx",
"args": [
"-y",
"bookmarks-mcp"
]
}
}
}Run this in your terminal
claude mcp add bookmarks -- npx -y bookmarks-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"bookmarks": {
"command": "npx",
"args": [
"-y",
"bookmarks-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"bookmarks": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bookmarks-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account Fisher521, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Your bookmarks, wherever they live, readable by your AI.
Everyone saves. Browsers, read-later apps, that Pocket export from 2023 — capture is a solved problem. Processing is not: the average bookmark is saved once and never touched again. AI assistants are the first thing that can actually process a pile like that — summarize, triage, turn it into a to-do list — but they can't see it.
This is a local, read-only MCP server that fixes the "can't see it" part.
One command in your MCP client config. Zero accounts. Nothing is ever sent to us.
| Source | How | Notes |
|---|---|---|
| Chrome, Edge, Brave, Arc, Vivaldi, Chromium | reads each profile's local Bookmarks file | every profile auto-detected |
| Safari (macOS) | reads ~/Library/Safari/Bookmarks.plist | includes your Reading List; no extension can do this — Safari's extension API has no bookmarks surface |
| Firefox | reads places.sqlite per profile | needs Node ≥ 22.5 (built-in sqlite); degrades gracefully below |
| Export files | Pocket CSV, Instapaper CSV, Raindrop CSV, browser HTML, URL lists | via parse-bookmarks |
Phone bookmarks: reachable once they sync to your desktop (iCloud → Safari on Mac, Chrome sync → desktop profile). There is no way for any third-party tool to read Safari bookmarks directly on iOS.
No account, no API key, no configuration — the server works the moment it's installed.
Claude Code:
claude mcp add -s user bookmarks -- npx -y bookmarks-mcp
Use `-s user`. The scope defaults to local, which only registers the server for the directory you ran the command in. Your bookmarks aren't tied to one project, so register it account-wide.
Claude Desktop / Cursor / any MCP client (mcpServers JSON):
{
"mcpServers": { "bookmarks": { "command": "npx", "args": ["-y", "bookmarks-mcp"] } } }
To run from source instead (for development), clone this repo next to its dependency parse-bookmarks (the two directories must be siblings), run npm install in bookmarks-mcp, and point your client at node /absolute/path/to/bookmarks-mcp/src/index.js.
macOS + Safari: the app hosting the server (Claude Desktop, your terminal) needs Full Disk Access (System Settings → Privacy & Security), because ~/Library/Safari is protected. Chromium browsers and Firefox need nothing.
| Tool | What it does |
|---|---|
list_sources | every bookmark source found on this machine |
list_bookmarks | list, with folder filter + pagination |
search_bookmarks | search titles / URLs / folders / tags |
recent_bookmarks | "what did I save this week?" |
bookmark_stats | the state of the pile: counts, age distribution, top domains |
parse_export_file | parse a Pocket/Instapaper/Raindrop/HTML export from disk |
export_bookmarks | everything out as Markdown, CSV, JSON, or importable browser HTML |
fetch_page_preview | a few-hundred-token preview of a page (title, description, headings, excerpt) instead of the raw HTML — for when title/URL alone can't be triaged |
The reason this exists. Ask your assistant:
Look at my bookmark stats, then help me triage: which of these become deep
reads, which are tools to try, which feed a project I'm working on, and
which should I finally let go? Give me a checklist for this week.
Or use the built-in triage_bookmarks prompt, which walks through exactly that — including asking *you* to define what your saves usually become, so the lanes are yours, not ours.
These are deliberate, not gaps waiting to be filled. PRs that cross them will be declined:
fetch_page_preview answers "is this worth my time" — it is not a reader mode and never will be a full-fidelity content extractor.Built by the team behind Burn 451, a read-later app. This server is deliberately neutral: it reads your bookmarks for whatever assistant and whatever workflow you choose, and it never writes to them.
MIT