
walkerOS Flow
io.walkerosPublished by walkeros.iov4.5.0Updated Oct 26, 2026
Build, validate, simulate, and deploy walkerOS event pipelines
Overview
Local walkerOS MCP server that lets an assistant build, validate, simulate, bundle and push walkerOS event pipelines.
- What you can do
- Validate and simulate walkerOS event flows locally
- Bundle and push flows from the local machine
- Work with what the walkerOS app stores via the hosted server
- Log in through an auth tool when no API token is supplied
- When to use it
- Useful when you work with walkerOS event tracking pipelines and want an assistant to check, simulate or deploy flow configurations from your own machine instead of the walkerOS app UI.
- Requirements
- Runs as a local stdio process started by the MCP client, installed from the npm package @walkeros/mcp (Node.js/npx). Optional settings: WALKEROS_TOKEN for the API token, WALKEROS_PROJECT_ID for a default project, and WALKEROS_APP_URL to override the app base URL. Network access is needed for cloud and hosted-server operations.
Installation
In SourceWeft
- Open walkerOS Flow in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@walkeros/mcp
The local walkerOS MCP server: validate, simulate, bundle and push flows on your own machine; the hosted server at https://app.walkeros.io/api/mcp covers what the walkerOS app stores.
Documentation • NPM Package • Source Code
Installation
Quick start
The server runs over stdio and is started by your MCP client. Add it to the client's configuration:
Documentation
Tools, resources, prompts, programmatic usage and the hosted server live in the docs: https://www.walkeros.io/docs/apps/mcp
Contribute
Feel free to contribute by submitting an issue, starting a discussion, or getting in contact.
License
MIT
Source: packages/mcps/mcp/README.md at commit e104d3e
Tools
0Version history
1- v4.5.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts