walkerOS Flow

Build, validate, simulate, and deploy walkerOS event pipelines

Connector by walkeros.ioOfficial · Domain verified by the MCP Registry

IndexedMITLocal (stdio)★ 347

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/walkeros-io-flow

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Build, validate, simulate, and deploy walkerOS event pipelines

Use cases: data-pipelines

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools: 5 read · 1 write · 2 delete
Secrets: 1 (API keys, tokens or passwords)
Install scripts: None found
Runs as: Node.js package

Tools by what they do 8

Read from the source code; the running server may list different tools.

Read 5 · Look things up without changing anything.

flow_examples
flow_load
flow_validate
package_get
package_search

Write 1 · Create, change, send or run things.

flow_bundle

Delete 2 · Delete, drop, revoke or wipe things.

flow_push
flow_simulate

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

WALKEROS_TOKEN

Other settings (environment variables or headers).

WALKEROS_APP_URL
WALKEROS_PROJECT_ID

Files it touches

Any path the agent passes to its tools

Tools (8)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

flow_bundleBundle Flow
Bundle a walkerOS flow configuration into deployable JavaScript. Resolves all destinations, sources, and transformers, then outputs a tree-shaken production bundle. Returns bundle statistics.
flow_examplesFlow Examplesread-only
List all step examples in a walkerOS flow configuration. Shows example names, step locations, and in/out shapes. Inline examples on a step take precedence; steps without inline examples fall back to the examples shipped by their referenced package. Each result is tagged with its source ("inline" or "package"). configPath: inline JSON, or a reference this server can read (locally a file path or an http(s) URL). Use this to discover available test fixtures and simulation data.
flow_loadLoad or Create Flowread-only
Load a flow configuration (inline JSON, or a reference this server can read; on your own machine a file path or an http(s) URL), or create a new empty flow by specifying a platform (web or server). Use the add-step prompt to add sources, destinations, transformers, or stores to the flow.
flow_pushPush Eventscan change or delete data
Push a real event through a walkerOS flow to actual destinations. Makes real API calls to real endpoints. Best suited for server-side flows; web flows should use flow_simulate for testing.
flow_simulateSimulate Flowcan change or delete data
Simulate events through a walkerOS flow without making real API calls. For destinations: event is a walkerOS event { name: "entity action", data: {...} }. For sources: event is { content, trigger?: { type?, options? } }, where content is the walkerOS event { name: "entity action", data: {...} }. Only the simulated source starts. step (required) targets the step to simulate, e.g. "destination.gtag". Use flow_examples to discover available test data. A destination simulation starts only its target destination. A source's own walker commands (e.g. a CMP's walker consent) are returned as elb calls…
flow_validateValidate Flowread-only
Validate walkerOS events, flow configurations, mapping rules, or data contracts. Accepts inline JSON, or a reference this server can read (on your own machine a file path or an http(s) URL). With only type and input, a flow runs every check on every flow and step, including each package's settings schema (fetched from the package CDN; offline: true skips that and says so). flow and path narrow the run; strict turns warnings and skips into failures: valid is false. Returns valid, errors and warnings with stable codes, and details.scope (what was checked), details.skipped (checks that could not …
package_getGet Packageread-only
Requires exact package name: do not guess names, use package_search first to find them. Returns schemas + hint texts + example summaries by default (lightweight). Use section parameter for full content: "hints" (with code blocks), "examples" (full in/out data), or "all".
package_searchSearch Packageread-only
Start here for package discovery. Never guess package names: use this tool first to find exact names. Without package name: returns catalog filtered by type/platform. With package name: returns metadata, hint keys, and example summaries.

Compare and alternatives

Featured in

Best MCP servers for deployment

Signals

Stars: 347
Forks: 23
Open issues: 3
Contributors: 18
Last commit (this folder): Oct 22, 2026 (6 days ago)
Last release: Oct 22, 2026 (6 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name: io.walkeros/flow
Version: 4.5.0
Auth: API key
Packages: npm @walkeros/mcp
License: MIT
Repository: github.com/elbwalker/walkerOS
Website: www.walkeros.io/docs/apps/mcp
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql