Developer · Local MCP server

walkerOS Flow

Build, validate, simulate, and deploy walkerOS event pipelines.

Visit walkerOS Flow's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.walkeros/flow
Version
4.5.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-09-02
Updated
2026-09-02
Publisher
io.walkeros · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain walkeros.io · how
Website
www.walkeros.io/docs/apps/mcp
Repository
github.com/elbwalker/walkerOS (folder packages/mcps/mcp)
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@walkeros/mcp4.5.0stdioWALKEROS_TOKEN (secret), WALKEROS_PROJECT_ID, WALKEROS_APP_URL

How to connect walkerOS Flow

walkerOS Flow runs locally from a Node.js package published to the npm registry: @walkeros/mcp version 4.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @walkeros/mcp@4.5.0. It reads these environment variables: WALKEROS_TOKEN (secret), WALKEROS_PROJECT_ID and WALKEROS_APP_URL; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "flow": {
      "command": "npx",
      "args": [
        "-y",
        "@walkeros/mcp@4.5.0"
      ],
      "env": {
        "WALKEROS_TOKEN": "<secret>",
        "WALKEROS_PROJECT_ID": "<value>",
        "WALKEROS_APP_URL": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from io.walkeros

All 2 →
ServerRunsEndpoint or package
walkerOS Source BrowserGenerate, parse, and validate walkerOS data-elb HTML tagging attributes.Local · stdionpm: @walkeros/mcp-source-browser

More developer servers

All 5,152 →
ServerRunsEndpoint or package
VulX WatchIndependent security review for AI-built apps. Watch a GitHub repo. Never a patch.Remote · HTTPLive check: sign-in requiredmcp.vulx.ai
VynixGive AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.Remote & Local · HTTP, stdioLive check: ✓ handshakemcp.vynix.in
W3cW3C MCP - web-standards lookup over w3c/browser-specs (GitHub, CF-reachable).Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
WaitbusWorkstation-local event bus: agents wait on or emit CI/pytest/Docker/filesystem events, no polling.Local · stdioPyPI: waitbus
Wapiworld WhatsApp APICheck your WhatsApp numbers, connection status and webhooks, and send a text when you confirm.Remote · HTTPLive check: ✓ handshakemcp.wapiworld.com
Waqi - AI Privacy LayerRedacts PII from your business tools before the AI sees them - with a provable audit log.Remote · HTTPwaqi.bilazann.com
WardenRegister every AI agent, log every action, prove it. EU AI Act compliance built in.Remote · HTTPLive check: ✗ no handshakewarden.flowvolt.io
WardenVerified context layer for AI coding agents - prunes, compresses, indexes, remembers. 32 MCP tools.Local · stdionpm: warden-ai