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 any web page as clean Markdown for AI agents: fetch, search, metadata, links. SSRF-safe.
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.vanshul.com/mcpRun this in your terminal
claude mcp add --transport http vanshulgoyal101 https://mcp.vanshul.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vanshulgoyal101": {
"url": "https://mcp.vanshul.com/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": {
"vanshulgoyal101": {
"type": "http",
"url": "https://mcp.vanshul.com/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.
ChatGPT connects only to servers on the internet:
https://mcp.vanshul.com/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 8, 2026
The registry name was verified with the GitHub account vanshulgoyal101, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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:★ 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.
MCP server for browser use access
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.
A public Model Context Protocol (MCP) server, running as a Cloudflare Worker, that lets any AI agent read the live web as clean Markdown. It builds on the same extraction pipeline as the sibling reader/ project (Mozilla Readability + Turndown), exposed over the MCP Streamable HTTP transport so agentic clients can plug straight in.
POST https://mcp.vanshul.com/mcp # JSON-RPC 2.0 (MCP)
GET https://mcp.vanshul.com/health # { ok: true, tools: [...] }
| Tool | Input | Returns |
|---|---|---|
fetch_markdown | { url, max_chars? } | The page's main content as clean Markdown (optionally truncated to max_chars) |
search_page | { url, query, max_matches?, context_chars? } | Only the passages matching query, each with its heading breadcrumb, ranked by relevance — token-efficient alternative to fetch_markdown |
fetch_metadata | { url } | JSON: title, byline, siteName, excerpt, wordCount |
extract_links | { url, limit? } | JSON: all outbound http(s) links + anchor text |
Remote/HTTP-capable clients (Claude Desktop, Cursor, Continue, …):
{
"mcpServers": { "web-reader": { "url": "https://mcp.vanshul.com/mcp" } } }
Stdio-only clients can bridge with mcp-remote:
npx mcp-remote https://mcp.vanshul.com/mcp
~/.cursor/mcp.json: { "mcpServers": { "web-reader": { "url": "https://mcp.vanshul.com/mcp" } } }
claude_desktop_config.json (Settings → Developer → Edit Config). If your version is stdio-only, use: { "mcpServers": { "web-reader": { "command": "npx", "args": ["mcp-remote", "https://mcp.vanshul.com/mcp"] } } }
web-reader with URL https://mcp.vanshul.com/mcp to your MCP servers config.curl -s https://mcp.vanshul.com/mcp \
-H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
curl -s https://mcp.vanshul.com/mcp \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":2,"method":"tools/call", "params":{"name":"fetch_markdown","arguments":{"url":"https://example.com"}}}'
curl -s https://mcp.vanshul.com/mcp \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":3,"method":"tools/call", "params":{"name":"search_page","arguments":{"url":"https://example.com","query":"more information"}}}'
mcp/
├── src/ │ ├── worker.ts # entry: routes /mcp, /health, rate limit, CORS │ ├── mcp.ts # JSON-RPC dispatch + tool definitions │ ├── extract.ts # HTML -> Markdown / links (Readability + Turndown) │ ├── search.ts # query-focused passage search over extracted Markdown │ ├── fetcher.ts # fetch with timeout, size cap, re-validated redirects │ └── security.ts # SSRF guard (block private/internal addresses) ├── public/ │ ├── index.html # landing page (served for non-API paths) │ ├── og.png # social share image (1200×630) │ ├── og.svg # social image source │ ├── robots.txt │ └── sitemap.xml ├── tests/ # vitest: security, extract, search, mcp dispatch, fetcher, worker ├── wrangler.toml ├── package.json ├── tsconfig.json └── README.md
cd mcp
npm install npm run typecheck npm test # vitest — security, extraction, search, MCP dispatch, fetcher, worker npm run dev # local worker at http://localhost:8787 (POST /mcp) npm run deploy # wrangler deploy
After the first deploy, attach the custom domain mcp.vanshul.com in the Cloudflare dashboard (Workers & Pages → this worker → Settings → Domains), or uncomment the [[routes]] block in wrangler.toml.
http(s) URLs; localhost, private ranges, cloud metadata and every redirect hop are blocked/re-validated.Implements initialize, ping, tools/list, tools/call and notifications (protocol version 2025-06-18). Tool failures are returned as { content, isError: true } so the agent can read the message and recover; malformed requests use standard JSON-RPC error codes.
MIT © Vanshul Goyal