About walkerOS Source Browser
A local MCP server for creating and checking walkerOS HTML tagging, intended for teams marking up pages with event attributes. It uses DOM parsing to generate, extract and validate `data-elb` attributes without an account or API token.
Key features
- 01Generate `data-elb` attributes and HTML
- 02Parse tagging from HTML snippets
- 03Validate tagging structure
- 04Support a custom attribute prefix
Use cases
- 01Add walkerOS tagging to a product card
- 02Extract events and globals from HTML
- 03Check a page for incomplete or unknown tagging
MCP support
Exposes three tagging tools and two documentation resources to MCP clients: `generate_tagging`, `parse_tagging` and `validate_tagging`. It runs locally over stdio and requires no account or API token.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
3Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| data | object | No | Entity properties as key:value pairs |
| link | object | No | Link relationships for data-elblink (id:type, e.g. {"details":"parent"}) |
| action | object | No | Trigger:action pairs for data-elbaction (nearest entity only) |
| entity | string | No | Entity name (creates data-elb="entity" and scopes data-elb-entity properties) |
| prefix | string | No | Custom prefix (default: data-elb) |
| scoped | object | No | Path-scoped generic properties for data-elb_ (only triggers nested below this element receive them) |
| actions | object | No | Trigger:action pairs for data-elbactions (all entities) |
| context | object | No | Context properties for data-elbcontext |
| globals | object | No | Global properties for data-elbglobals |
Details
From the project README
@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. Runs locally, 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"]
}
}
}
In Claude Code you can install the walkerOS plugin instead, which registers this server along with the flow development server and the walkerOS skills:
/plugin marketplace add elbwalker/walkerOS
/plugin install walkeros@elbwalker
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 orphan actions, missing entities, unknown triggers, 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.