walkerOS: event collection plugin for Claude Code
walkerOS
The walkeros plugin for Claude Code: 22 skills and two MCP servers for event collection, flows and tracking validation
- 347 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Through a walkerOS account the agent gets the right to create and change tracking projects and deployments
- The skills steer the agent to bundle scripts and run npx walkeros, that is, to execute code on your machine
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/walkerosDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Through a walkerOS account the agent gets the right to create and change tracking projects and deployments
- The skills steer the agent to bundle scripts and run npx walkeros, that is, to execute code on your machine
This is third-party code. Review the repository files before installing.
What it does
The walkeros plugin for Claude Code teaches the agent the walkerOS platform: it carries 22 skills and two MCP servers. walkerOS is an open event collection platform. It takes events from the browser, dataLayer, Express and cloud functions, processes them with consent in mind and sends them to GA4, Google Ads, Meta CAPI, BigQuery and other destinations. Configuration lives as code: flows are described in JSON or TypeScript and reviewed in pull requests. The basic skills explain events, flows, sources and destinations, as well as transformers and stores. Others help create a new source, destination or transformer and set up mapping. Separate skills cover testing strategy and debugging, and walkeros-using-cli covers the walkeros command line, for example bundling a flow with `npx walkeros bundle flow.json`. The local walkeros-flow MCP server runs through npx @walkeros/mcp: it loads a flow, validates it and simulates an event. The hosted server at https://app.walkeros.io/api/mcp manages projects and deployments on the walkerOS side. An extra package, @walkeros/mcp-source-browser, is connected with a separate entry.
Who it is for. For developers and analysts who set up event collection and site tracking in walkerOS and want Claude Code to know the platform and validate flows.
Good fit when
- You need to write a new event destination for walkerOS by the platform's rules without studying the code from scratch
- A flow must be validated and a test event run locally before deployment
- You need to set up event mapping to a GA4 or Meta format and describe it in configuration
- You want a standalone script bundled from a JSON configuration with npx walkeros bundle
- The team moves off Google Tag Manager and keeps tracking as code in the repository
Not a fit when
- You do not use walkerOS: the skills and servers concern this platform only
- You need web analytics reports: the plugin collects and routes events, and reports come from destinations like GA4 or BigQuery
- Your organization's rules forbid connecting the hosted server: it needs a walkerOS account
- The client is not Claude Code: the plugin installs with /plugin commands, and for other agents the servers are added by hand
Example request
Validate the flow in flow.json, run a test page view event and show where it would go.Limitations
The plugin installs only into Claude Code; for other MCP clients the servers are added as a configuration entry. The local walkeros-flow server runs through npx, so it needs Node.js.
Local operations (loading and validating a flow, simulating an event) need no account. The hosted server works through a platform account, so connect it only when the agent needs rights over projects.
The skills cover development inside walkerOS and do not replace the documentation of specific destinations such as GA4 or Meta CAPI. The project itself ships under the MIT license. Whether app.walkeros.io is reachable from Russia has not been checked.
How to disable. Run /plugin uninstall walkeros@elbwalker in Claude Code, then remove the marketplace entry if you no longer use it.
FAQ
How do I install the walkerOS plugin in Claude Code?
Run /plugin marketplace add elbwalker/walkerOS, then /plugin install walkeros@elbwalker. The plugin installs the skills and both MCP servers at once.
Do I need a walkerOS account?
Not for local work: loading a flow, validating it and simulating an event happen on your computer. Only the hosted server needs an account.
What do the plugin skills do?
They teach the agent the platform: events, flows, sources and destinations, mapping, tests and debugging. There are also skills for creating a new source, destination, transformer or consent source.
How do I connect the MCP servers without Claude Code?
Add two servers to the MCP client configuration: walkeros-flow with the command npx and the argument @walkeros/mcp, and walkeros-source-browser with the argument @walkeros/mcp-source-browser.
How does walkerOS differ from Google Tag Manager?
The event flow is a file in the repository and passes schema validation before deployment. Events wait for user consent and only then go to every destination. A detailed comparison with GTM is in the documentation on walkeros.io.
Discussion
No questions or reviews yet.
Related
PluginsAn MCP server for Google Ads, Reddit Ads and GA4: the agent reads reports and edits campaigns, and only you turn on real spend
A set of eight SEO and GEO skills for Claude running on real Search Console, GA4 and ads data through the Ryze MCP
Eight read-only SEO MCP servers
seo-tools-mcp
SERP, Wordstat, GSC, GA4, Yandex Webmaster, Metrika and A-Parser: eight read-only MCP servers with strict JSON and multi-account support for Claude Code
A self-hosted MCP server on Cloudflare Workers for local SEO: organization search and cards in 2GIS, Yandex Geocoder and Google Places
A Rust MCP server for Ozon Seller, Ozon Performance and part of Wildberries analytics: 76 read-only tools, no data-changing method at all
An open set of 48 marketing skills for agents: SEO and GEO, ad audit and management, GA4 and Search Console analytics, WordPress and CRM operations
README in short
The documentation splits installation into two modes: importing into a TypeScript app and bundling a standalone script from JSON. The AI section covers installing the plugin and configuring the servers by hand.