Generates, parses, and validates walkerOS data-elb HTML tagging attributes using real DOM parsing.
Also known as elbwalker/walkerOS, source-browser, @walkeros/mcp-source-browser
- Stars
- 350
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- 4.5.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is walkerOS Source Browser MCP?
walkerOS Source Browser is an MCP server. Generates, parses, and validates walkerOS data-elb HTML tagging attributes using real DOM parsing. It exposes 3 tools, such as generate_tagging, parse_tagging, validate_tagging.
Summary generated from the project's README
About walkerOS Source Browser MCP server
Managing walkerOS HTML tagging attributes becomes more accurate when an AI assistant can generate, parse, and validate data-elb attributes using real DOM parsing. Developers use this local MCP server to ensure that structured input is correctly converted into HTML snippets and that the resulting tagging follows specific rules. It runs via stdio through an MCP client and requires no API keys or external accounts to function.
The server provides three specific tools to manage the tagging lifecycle. The generate_tagging tool creates data-elb attributes and HTML examples from structured data, while parse_tagging extracts events and globals from existing snippets. To ensure quality, the validate_tagging tool checks for errors like empty entity names, orphan actions, unknown triggers, or entities missing actions. Users can also specify a custom prefix for these attributes instead of the default data-elb setting.
What you can do with it
- 1Create HTML tagging snippetsAsk your assistant to produce ready-to-paste data-elb attributes for specific UI components like product cards.
- 2Extract event data from HTMLProvide an HTML snippet to an AI client to identify the walkerOS events and globals it contains.
- 3Verify tagging accuracyUse the validation tool to find orphan actions, unknown triggers, or entities that lack required actions.
Written from the project's README. Every use case is checked against a quote from it.
How to install walkerOS Source Browser MCP
Formats verified 10 Nov 2026Install walkerOS Source Browser MCP in Claude Code
$ claude mcp add source-browser -- npx -y @walkeros/mcp-source-browserInstall walkerOS Source Browser MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"source-browser": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}Install walkerOS Source Browser MCP in VS Code
.vscode/mcp.json
{
"servers": {
"source-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}Install walkerOS Source Browser MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"source-browser": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}Install walkerOS Source Browser MCP in Codex
~/.codex/config.toml
[mcp_servers.source-browser] command = "npx" args = ["-y", "@walkeros/mcp-source-browser"]
Install walkerOS Source Browser MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"source-browser": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp-source-browser"
]
}
}
}walkerOS Source Browser MCP tools 3
Detected from the READMEgenerate_taggingparse_taggingvalidate_tagging
| generate_tagging | — | |
| parse_tagging | — | |
| validate_tagging | — |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@walkeros/mcp-source-browser
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
Installation
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
Quick start
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.
Tools
| 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.
Resources
| URI | Content |
|---|---|
walkeros://docs/tagging/html-attributes |
Guide to data-elb HTML attribute tagging |
walkeros://docs/tagging/tagger |
createTagger() fluent API reference |
Documentation
Full parameter tables and examples live in the docs: https://www.walkeros.io/docs/apps/mcp
Contribute
Feel free to contribute by submitting an issue, starting a discussion, or getting in contact.
License
MIT
walkerOS Source Browser MCP questions
How do I add walkerOS Source Browser MCP to Claude Code?
Run claude mcp add source-browser -- npx -y @walkeros/mcp-source-browser in your terminal. Add --scope user to make it available in every project.
How do I add walkerOS Source Browser MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does walkerOS Source Browser MCP provide?
It exposes 3 tools, including generate_tagging, parse_tagging, validate_tagging.
How do I install the server?
You can run it via npx using @walkeros/mcp-source-browser or install the binary directly using npm install @walkeros/mcp-source-browser.
Does this server require an API key?
No, the server runs locally and does not require an account or an API token.
What tools are available in this server?
The server provides tools to generate tagging, parse HTML snippets to extract walkerOS events, and validate tagging for errors like orphan actions or unknown triggers.