walkerOS Source Browser

io.walkerosPublished by walkeros.iov4.5.0Updated Oct 24, 2026

Generate, parse, and validate walkerOS data-elb HTML tagging attributes

The publisher's own server: Source

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local MCP server that lets an assistant generate, parse and validate walkerOS data-elb HTML tagging attributes.

What you can do
  • Generate data-elb attributes and an example HTML snippet from structured input
  • Parse an HTML snippet and extract the walkerOS events and globals it produces
  • Validate tagging for orphan actions, missing entities, unknown triggers and entities without actions
  • Read bundled reference docs on data-elb HTML attributes and the createTagger() API
When to use it
Useful when you are adding walkerOS analytics tagging to a page and want the assistant to write the data-elb attributes and then check its own output for structural mistakes.
Requirements
Runs as a local stdio process, typically started with npx from the npm package @walkeros/mcp-source-browser; Node.js and npm are needed. No account, API token, environment variables or headers are required.
Before you install
It only generates, parses and validates markup locally; no credentials are requested. Review generated attributes before pasting them into production pages, since validation covers structural issues such as orphan actions or missing entities, not whether the tagging matches your analytics intent.

Installation

In SourceWeft

  1. Open walkerOS Source Browser in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[walkerOS]

@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:

json
{  "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:

bash
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

ToolDescription
generate_taggingTurn structured input into data-elb attributes and an example HTML snippet
parse_taggingParse an HTML snippet and extract the walkerOS events and globals it produces
validate_taggingCheck 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

URIContent
walkeros://docs/tagging/html-attributesGuide to data-elb HTML attribute tagging
walkeros://docs/tagging/taggercreateTagger() 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

Source: packages/mcps/source-browser/README.md at commit f6ff0b9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v4.5.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Source integrations