walkerOS Flow

Name: walkerOS Flow
Author: elbwalker

Build, test and deploy walkerOS event-tracking flows from an AI assistant, locally or in the walkerOS app

Official · elbwalker TypeScript Remote (hosted) · Streamable HTTP Local · stdio Data and analytics Developer tools Cloud platforms

GitHub npm Website

52 popularity score ★ 349 ↓ 438/wk

Connect your client

Remote (hosted)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude (desktop and web)Settings, Connectors, Add custom connector, URL https://app.walkeros.io/api/mcp

https://app.walkeros.io/api/mcp

Claude Codeterminal, then /mcp in Claude Code to sign in

claude mcp add --transport http walkeros https://app.walkeros.io/api/mcp

CursorMCP server settings, URL https://app.walkeros.io/api/mcp

{
  "mcpServers": {
    "walkeros-flow": {
      "url": "https://app.walkeros.io/api/mcp"
    }
  }
}

Local (npm)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal

claude mcp add walkeros-flow -- npx @walkeros/mcp

Claude Desktopclaude_desktop_config.json

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

Cursor~/.cursor/mcp.json

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

VS Code.vscode/mcp.json

{
  "servers": {
    "walkeros-flow": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "@walkeros/mcp"
      ]
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.walkeros-flow]
command = "npx"
args = ["@walkeros/mcp"]

Gemini CLITerminal

gemini mcp add --scope user walkeros-flow npx -- @walkeros/mcp

Settings 3

`WALKEROS_TOKEN`	Optional: Automation token (wos_pat_...) for the app tools; an alternative to logging in with the auth tool. Not needed for local tools.
`WALKEROS_PROJECT_ID`	Optional: Default project (proj_...) for calls that name none; local server only.
`WALKEROS_APP_URL`	Optional: walkerOS app base URL; defaults to https://app.walkeros.io.

What it does

walkerOS Flow is the MCP server published by the walkerOS project (elbwalker) for working on walkerOS flows: the JSON configurations that wire event sources, transformers, a collector and destinations such as GA4 into a tracking pipeline. It ships as the npm package @walkeros/mcp and runs over stdio on your own machine; the same tool set is also offered as a hosted endpoint inside the walkerOS app.

The local tools need no account. They load a flow from a file, URL or inline JSON (or start an empty web or server flow), validate events, flows, mapping rules and data contracts against package schemas, simulate an event through one step without calling any vendor, bundle a flow into deployable JavaScript, list step examples, and browse or inspect walkerOS packages from npm. flow_push is the exception among them: it sends a real event to the real destinations.

With a walkerOS app login the app tools manage projects, saved flows and previews, deployments, flow secrets, Observe sessions that show how live events travelled through each step, release history and notes, and tagged page frames. Answers about app objects carry an appUrl link to the matching screen.

The package's own tool roster (surface.json in version 4.8.0) lists 19 tools; the docs page describes 18 and leaves out feedback, which submits feedback text to the walkerOS team, optionally with user and project details. The server also exposes reference resources (flow schema, event model, mapping, consent, variables) and three prompts: add-step, setup-mapping and manage-contract.

What it needs

To run it yourself	Node.js 20+

Node.js 20 or newer (the package's engines field) to run `npx @walkeros/mcp`. The local flow tools need nothing else. The app tools need a walkerOS account whose plan includes the mcp feature; hub_manage also needs the hub feature and frame_manage the frames feature. Sign in through the auth tool (a browser device-code approval) or set WALKEROS_TOKEN to an automation token (wos_pat_...). The hosted endpoint signs in with OAuth; in Claude Code run /mcp after adding it to finish sign-in.

Limits

flow_push makes real API calls and is meant for server-side flows: web destinations need browser globals that Node.js lacks. On the hosted endpoint, tools that take a file path read the app server's disk, not yours, so give inline JSON or a flow ID; local package paths there are reported as skipped (SCHEMA_UNAVAILABLE). Deploys wait up to 12 minutes locally (10 hosted) unless wait is false. observe_journeys returns 50 journeys by default, up to 100. hub_manage writes are additive with no delete, and threads can only be resolved in the app. The hosted door ignores WALKEROS_PROJECT_ID and forgets set_default on reconnect. Calls to features outside your plan answer FEATURE_NOT_AVAILABLE.

Who it suits

Suits teams who already build tracking with walkerOS and want an assistant to draft, validate and simulate flows locally without an account, and, with a walkerOS plan that includes MCP, to save, deploy and observe them in the walkerOS app. It is of little use without walkerOS: it does not configure GA4 or other vendors directly. Pick the hosted endpoint when you only need app work and no local files; pick the local npx server when flows live in files on your machine. For data-elb HTML tagging the same project ships a separate server, @walkeros/mcp-source-browser.

Tools 19

flow_load: Opens a flow from a file, URL, inline JSON or saved app ID, or starts an empty web or server flow
flow_validate: Checks an event, flow, mapping or contract and returns errors and warnings with stable codes
flow_bundle: Builds a flow into deployable JavaScript, with optional size stats and output file
flow_simulate: Runs an event through one step of a flow without real vendor calls, secrets masked
flow_push: Sends a real event through a flow to its actual destinations
flow_examples: Lists the in/out examples of each step, falling back to package examples
package_search: Browses the walkerOS package catalogue by type and platform or looks up one package
package_get: Fetches a package's schemas, hints and examples from npm
diagnostics: Reports MCP and CLI versions, app URL, app health and API contract compatibility
auth: Shows login status, logs in through a browser device-code approval, or logs out
project_manage: Lists, reads, creates, renames, deletes or selects a default walkerOS project
flow_manage: Lists, reads, creates, updates, duplicates and deletes saved flows and their previews
deploy_manage: Deploys a flow and lists, reads or deletes deployments
secret_manage: Lists, sets, rotates or deletes a flow's secrets; values are never returned
observe_session: Starts, checks or stops an Observe session on a flow
observe_journeys: Reads the step-by-step journeys of events in an active Observe session
hub_manage: Reads release history and diffs, and adds release rationale and discussion notes
frame_manage: Lists tagged page frames of a flow and reads their marks
feedback: Sends feedback text to the walkerOS team, anonymous or with user and project info

Popularity

52 popularity score, on our list (the bar is 36)

★ 349 ↓ 438/wk

GitHub stars, whole repository	349	21.1 points
Stars in 30 days	+1	1.5 points
npm downloads, last week	438	21.1 points
Official server	Yes	8 points

It lives in the folder packages/mcps/mcp of elbwalker/walkeros, which holds more than this server. Its stars are the whole repository's, so in the score they never count for more than its own downloads.

Measured 2026-11-08. How the score works.

Where it is published

Code	elbwalker/walkeros/packages/mcps/mcp ★ 349, the whole repository
npm	@walkeros/mcp 4.9.0, 2026-11-04
Hosted	`https://app.walkeros.io/api/mcp` Streamable HTTP · OAuth sign-in

What it can reach

Runs	On your machine, or on the maker's servers
Reaches	Files on your machine, The internet, Your account at a service, Cloud resources
Changes things	Yes: it can write, send, create or delete
Sign-in	OAuth sign-in for the hosted endpoint; none to run it yourself
Licence	MIT (npm)
Last code change	2026-11-04

Runs locally over stdio. The local tools read flow files and URLs you name, fetch package schemas from npm, and flow_bundle can write an output file; flow_push sends real events to the destinations a flow configures. App tools act as the signed-in walkerOS user across every project they belong to: they can create, change and delete flows, projects and deployments, deploy flows, and set or rotate flow secrets (values are encrypted at rest and never returned). Sign-in is a device-code grant with a self-refreshing session, revocable under Account, Connected apps, or an automation token with read or read-and-write scope. On the hosted endpoint tools run on walkerOS servers. The feedback tool sends text to walkerOS, with user and project info unless anonymous.

Over time

GitHub stars, whole repository 349 +1

349347

9 Oct 20268 Nov 2026

npm downloads a week 438 −96 (−18 %)

1.3k34

23 Feb 20268 Nov 2026

Before the site measured it, read from npm's daily download counts.

Popularity score 52 −3 (−5 %)

5542

9 Oct 20268 Nov 2026

What is rising across the directory

Sources

Page checked 2026-10-15.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![walkerOS Flow on EveryMCPServer](https://everymcpserver.com/badge/walkeros-flow.svg)](https://everymcpserver.com/servers/walkeros-flow)

Connect your client

Add in one click

Or add it by command or config

Add in one click

Or add it by command or config

Settings 3

What it does

What it needs

Limits

Who it suits

Tools 19

Similar servers

tapflow

itasca-mcp

Agentic Flow

autocontext

Blitz

agentistics