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)
Generate, parse, and validate walkerOS data-elb HTML tagging attributes
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
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"source-browser": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}Run this in your terminal
claude mcp add source-browser -- npx -y @walkeros/mcp-source-browserPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"source-browser": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"source-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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 5, 2026
The registry name was verified against the domain walkeros.io (the registry checks domain ownership)
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Needs the server’s tool list first; this check starts in the next step
Compared only with servers in this prototype, not the whole registry.
It passed 3 of 3 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 yesterday, and the latest version (4.5.0) reached the registry 2 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:★ 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.
Model Context Protocol server for walkerOS HTML tagging. Generates, parses, and validates data-elb attributes using real DOM parsing, so an AI assistant can tag a page and check its own work. It runs locally and needs no account or API token.
Documentation • NPM Package • Source Code
The server runs over stdio and is started by your MCP client. Add it to the client's configuration:
{
"mcpServers": { "walkeros-source-browser": { "command": "npx", "args": ["@walkeros/mcp-source-browser"] } } }
The walkerOS Claude Code plugin registers the flow servers and the walkerOS skills. It does not register this server, so in Claude Code add it to the configuration as above too.
To install the binary directly:
npm install @walkeros/mcp-source-browser
Ask your assistant to tag a page, for example: "Generate walkerOS tagging for a product card with name and price". It calls generate_tagging and returns ready-to-paste data-elb attributes.
| Tool | Description |
|---|---|
generate_tagging | Turn structured input into data-elb attributes and an example HTML snippet |
parse_tagging | Parse an HTML snippet and extract the walkerOS events and globals it produces |
validate_tagging | Check tagging for empty entity names, orphan actions, unknown triggers, orphan properties, and entities without actions |
All three accept an optional prefix to match a custom attribute prefix, which defaults to data-elb.
| URI | Content |
|---|---|
walkeros://docs/tagging/html-attributes | Guide to data-elb HTML attribute tagging |
walkeros://docs/tagging/tagger | createTagger() fluent API reference |
Full parameter tables and examples live in the docs: https://www.walkeros.io/docs/apps/mcp
Feel free to contribute by submitting an issue, starting a discussion, or getting in contact.
MIT