# walkerOS Flow — MCP server card for AI agents

Build, validate, simulate, and deploy walkerOS event pipelines

Registry name: `io.walkeros/flow` · category: Cloud and DevOps · version 4.5.0 · updated 2026-09-02

## Connect
- npm (stdio): `npx -y @walkeros/mcp`

## Facts
- Repository: https://github.com/elbwalker/walkerOS (351 stars)
- Website: https://www.walkeros.io/docs/apps/mcp

Before you connect a server: read its repository, and give it only the permissions and keys it needs.

## Links
- AgentGid page: https://agentgid.com/mcp/servers/io-walkeros-flow/


## walkerOS Flow: build and test tracking setups with AI

walkerOS is an open source way to collect site and app events, such as page views and purchases. It sends them to tools like GA4, ad platforms or a data warehouse. This server lets your AI assistant create that setup, check it, try events on it without sending anything, and bundle it for your site. A hosted version also works on flows saved in the walkerOS app.

### Where to use it
- Set up GA4 tracking by asking: Ask for a web setup that sends events to GA4, and the assistant creates it, checks it and tries a page view, all on your computer with no account.
- Try an event before it goes live: Send a test page view through your setup file and see which tools would receive it, without calling any of them.
- Map events to a destination's fields: Let the assistant write the rules that turn your events into the shape a tool such as gtag expects, using the package's own examples.
- Learn what a destination needs: Ask what settings a destination, for example Snowplow, needs, and get its options, hints and examples before you write anything.
- Bundle the setup for your site: Turn the checked setup into one small script file for your site or server, with only the parts it uses.
- Deploy a saved flow: With a walkerOS account and the hosted server, ask the assistant to deploy your checkout flow and report when it is live.

### How to start
- In Claude Code, add the walkerOS plugin. It installs the local server, adds the hosted one and adds walkerOS skills.

```
/plugin marketplace add elbwalker/walkerOS
/plugin install walkeros@elbwalker
```

- In other assistants, add the local server to the configuration; it starts by itself when needed.

```
{
  "mcpServers": {
    "walkeros-flow": {
      "command": "npx",
      "args": ["@walkeros/mcp"]
    }
  }
}
```

- Ask for a flow, then have it validated and simulated before anything is bundled or pushed.

### License
Free and open source under the MIT license, also for paid products. The hosted server needs a walkerOS account.

### Good to know
- flow_push sends real events to the real destinations, such as your analytics or ad accounts. Use flow_simulate to try things.
- The local server reads files and web addresses on your computer and writes bundles to disk. The hosted server cannot see your files.
- A client connected to the hosted server acts as you. It can change, deploy and delete flows and manage secrets in every project you belong to.
- Usage statistics are off unless you opt in on the command line; after opting out, restart a running server.

Checked 2026-11-10 against: https://www.walkeros.io/docs/apps/mcp, https://www.walkeros.io/docs/apps/telemetry, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/README.md, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/LICENSE, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/README.md, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/server.json, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/server.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/stdio.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/specs.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/tool-handlers.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/telemetry.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/tools/validate.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/tools/push.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/tools/bundle.ts, https://github.com/elbwalker/walkerOS/blob/dedbdf71653b227f3f61e4c615a6aa4530b89dda/packages/mcps/mcp/src/tools/simulate.ts, https://registry.npmjs.org/@walkeros/mcp/4.9.0, https://registry.npmjs.org/@walkeros/mcp/-/mcp-4.9.0.tgz

### Mistakes to avoid
- Don't: Calling flow_push to test a new setup → Do: Use flow_simulate first; call flow_push only on purpose, and preferably for server flows. (flow_push makes real calls to real destinations, and web destinations need browser globals Node.js lacks.)
- Don't: Passing inline flow text as configPath to flow_bundle → Do: Pass a file path or a web address. (flow_bundle reads the value as a file name and fails.)
- Don't: Writing a config loaded with flow_load straight back to disk → Do: Remove the user_data wrapper from each string value first. (Values people wrote come back wrapped, and the wrapper would become part of the value.)
- Don't: Guessing a package name for package_get → Do: Call package_search first and use the exact name it returns. (package_get needs the exact package name.)
- Don't: Validating the structured output of every tool with the MCP TypeScript SDK client → Do: Read the text block or skip output-schema validation for flow_load, flow_examples, flow_bundle and flow_simulate. (Their advertised output schemas leave out fields the results carry, so a validating client rejects the results.)

### Questions
- Do I need a walkerOS account? Not for the local server. Creating, checking, simulating and bundling flows runs on your computer with no account; deploying saved flows needs the hosted server and an account.
- Does simulating send data to Google or other tools? No. flow_simulate makes no real calls; only flow_push does.
- Does the server send usage data to walkerOS? Only if you opted in with walkeros telemetry enable. It then sends tool names, outcomes and timings, never file contents or flow settings.
- Can a saved flow in the walkerOS app be tested locally? Yes. The hosted server gives a config link that lasts about ten minutes, and the local tools read the config from it.

---
AgentGid's catalog is curated: every entry was checked against the maker's official pages (registry, repository, license and pricing pages) on the date shown; a license value shows the quote it stands on wherever AgentGid has one. Usage numbers come from AgentGid's own scan of public repositories set up for AI coding agents. Claims by makers are reported, not tested by AgentGid.
