Mmcp.market

walkerOS Flow MCP server

by walkeros.io·io.walkeros/flow·v4.5.0
No reviews yet

Build, validate, simulate, and deploy walkerOS event pipelines

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Established

344 stars271 downloads/wk

Reviews

Write one

Nobody has reviewed walkerOS Flow yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

walkerOS Flow tools (16, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • auth

    Manage walkerOS authentication. Check login status, log in via device code flow, or log out. No terminal or browser required, the MCP client handles the authorization URL.

  • deploy_managewrite action

    Deploy walkerOS flows and manage deployments. For get/delete actions pass flowId (required) plus optional slug to disambiguate when a flow has multiple active deployments. If a flow has >=2 active deployments and no slug is supplied, the tool returns a MULTIPLE_DEPLOYMENTS error with a details[] list showing each deployment's slug, type, status, and updatedAt.

  • feedbackwrite action

    Send feedback about walkerOS

  • flow_bundle

    Bundle a walkerOS flow configuration into deployable JavaScript. Resolves all destinations, sources, and transformers, then outputs a tree-shaken production bundle. Returns bundle statistics. Set remote: true to use the walkerOS cloud service instead of local build tools.

  • flow_examples

    List all step examples in a walkerOS flow configuration. Shows example names, step locations, and in/out shapes. Use this to discover available test fixtures and simulation data.

  • flow_load

    Load an existing flow configuration from a local file path, URL, or walkerOS API (by flow ID). 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_manage

    Manage walkerOS flows and their previews. List/get/create/update/delete/duplicate flows, or create/inspect/delete preview bundles for testing flow changes on live sites.

  • flow_push

    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_simulate

    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? }, env?: {...} }. Use step to target a specific step. Use flow_examples to discover available test data. IMPORTANT: Destinations with require (e.g. require: ["consent"]) stay pend

  • flow_validate

    Validate walkerOS events, flow configurations, mapping rules, or data contracts. Accepts JSON strings, file paths, or URLs as input. Returns validation results with errors, warnings, and details.

  • observe_journeys

    Read the assembled, cross-runtime journeys for a flow that is currently being observed (an active Observe session). Pass flowId; the active session is resolved for you (a flow has at most one). Each journey is one traced event reconstructed end to end across web and server: its ordered hops, per-hop status, captured in/out payloads, consent, and vendor calls. When the flow has no active session th

  • observe_session

    Open, inspect, or end an Observe session: a time-boxed window on one flow that runtimes attach to as arms. A preview arm streams from a browser, a container arm runs server-side, and both feed ONE shared journeys feed. start opens the window (arms picks which runtimes attach), status reports per-arm state plus recordsReceived and expiresAt, stop ends the whole session including every arm. A flow h

  • package_get

    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_search

    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.

  • project_manage

    Manage walkerOS projects. List, create, update, delete projects, or set a default project for CLI operations.

  • secret_manage

    Manage a flow\u2019s managed secrets (the $secret.<NAME> values its steps reference at deploy/run time). Actions: list (metadata only), set (create), update (rotate value), delete. Secrets are write-mostly: values are encrypted at rest and are NEVER returned, listed, or echoed. Reference a secret from a flow step as $secret.<NAME> (credentials, tokens, and private keys use $secret, not $env).

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the walkerOS Flow repository's README, as published. We do not edit it. Read it on GitHub

Event collection you own, version, and trust

From browser to BigQuery and ad platforms - warehouse-native, and ready for AI agents via MCP.

The problem

GA4, custom tags, ad pixels - each one a separate setup, none of them agreeing on the same numbers. When something breaks, you can't see where.

walkerOS is one collection layer for all of them.

Why walkerOS?

with confidence

  • Config-as-code - version control your tracking, review it in PRs, deploy

to every destination

  • Declarative tagging - tag your UI in HTML, not scattered JavaScript
  • Consent-native - events queue until consent is given, then flush correctly

in a dashboard

  • Schema validation - catch bad events at collection time, not weeks later

from a single event definition

  • One layer, many destinations - send to your warehouse and ad platforms

warehouse, ready to query

  • Warehouse-native - events land clean and structured in your data
  • MIT licensed - self-host anywhere, no vendor lock-in

How it works

GCP Functions, and more)

  • Sources: Where events come from (browser, dataLayer, Express, AWS Lambda,

enrichment)

  • Collector: The processing engine (consent, validation, mapping, routing,

more)

  • Destinations: Where events go (GA4, Google Ads, Meta CAPI, BigQuery, and

Two ways to install walkerOS

Choose one based on your workflow and integration possibilities:

Integrated (import into your app):

import { startFlow } from '@walkeros/collector';

const { elb } = await startFlow({
  destinations: {
    console: {
      code: {
        type: 'console',
        config: {},
        push: (event) => console.log('Event:', event.name),
      },
    },
  },
});

await elb('page view', { title: 'Home' });
// -> logs: Event: page view

Wire a real source and destination once you are ready:

import { startFlow } from '@walkeros/collector';
import { sourceBrowser } from '@walkeros/web-source-browser';
import { destinationGtag } from '@walkeros/web-destination-gtag';

await startFlow({
  sources: {
    browser: {
      code: sourceBrowser,
      config: { settings: { pageview: true } },
    },
  },
  destinations: {
    ga4: {
      code: destinationGtag,
      config: {
        settings: { ga4: { measurementId: 'G-XXX' } },
      },
    },
  },
});

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y @walkeros/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add flow -- npx -y @walkeros/mcp
Add to Cursor

walkerOS Flow: common questions

Is walkerOS Flow MCP server safe?
Mostly: it is graded B (83/100). Read the walkerOS Flow safety report
How do I install walkerOS Flow?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does walkerOS Flow need an API key?
Yes. The registry entry asks for WALKEROS_TOKEN.
Is walkerOS Flow maintained?
The last commit was 4 days ago (2026-09-16). The latest release is v4.5.0.
What can I use instead of walkerOS Flow?
Servers from other publishers that do the same job: Gitlab MCP server, Omnara MCP server and Aiven MCP server. Compare all walkerOS Flow alternatives.

Alternatives to walkerOS Flow

Same job from other publishers: the closest match first, then the best rated.

All walkerOS Flow alternatives →
  • Gitlab
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • Omnara
    Deploy durable AI agents with Omnara, an open-source managed-agent platform.
    A
  • Aiven MCP
    Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.
    A
  • ShipStatic
    Deploy static websites from AI agents. Free at mcp.shipstatic.com — no install, no signup.
    A
  • Mockzilla
    Mock OpenAPI specs locally, or log in to deploy hosted mocks on mockzilla.org from your MCP client.
    C
walkerOS Flow vs GitlabwalkerOS Flow vs OmnarawalkerOS Flow vs Aiven MCP

More from walkeros.io →