Skip to content
mcp/skillhub

walkerOS Flow MCP Server

by elbwalkerio.walkeros/flowv4.5.0

MCP server for walkerOS flow development - discover packages, scaffold configs, validate, bundle, simulate, and test event pipelines

348Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active3d ago

Install walkerOS Flow MCP server

Install in Claude Code

claude mcp add elbwalker -e WALKEROS_TOKEN='<walkeros-token>' -- npx -y @walkeros/mcp

Configuration

VariableRequiredSecretDescription
WALKEROS_TOKEN—yeswalkerOS API token. Optional, the local tools work without it and the auth tool can log in instead.
WALKEROS_PROJECT_ID——Default walkerOS project id (proj_...) used by the cloud tools.
WALKEROS_APP_URL——Base URL override for the walkerOS app. Defaults to https://app.walkeros.io.

Freshness

Active — last maintenance signal 3d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-07 · 3d ago · GitHub

  2. Latest release

    2026-10-06 · 4d ago · GitHub · v4.7.2

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-09-02 · 37d ago · official registry · v4.5.0

FAQ

›How do I install the walkerOS Flow MCP server in Claude Code?

Run: claude mcp add elbwalker -e WALKEROS_TOKEN='<walkeros-token>' -- npx -y @walkeros/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does walkerOS Flow require an API key?

Yes. It expects WALKEROS_TOKEN, of which 1 is a secret.

›Can I use walkerOS Flow as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is walkerOS Flow in the official MCP registry?

Yes, as io.walkeros/flow.