Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @walkeros/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
WALKEROS_TOKEN=<secret> WALKEROS_PROJECT_ID=<value> WALKEROS_APP_URL=<value> claude mcp add io.walkeros-flow -- npx -y @walkeros/mcp@4.5.0Ejecútalo en una terminal.
{ "mcpServers": { "io.walkeros-flow": { "command": "npx", "args": [ "-y", "@walkeros/[email protected]" ], "env": { "WALKEROS_TOKEN": "<secret>", "WALKEROS_PROJECT_ID": "<value>", "WALKEROS_APP_URL": "<value>" } } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
From browser to BigQuery and ad platforms - warehouse-native, and ready for AI agents via MCP.
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.
Build, validate, simulate, and deploy walkerOS event pipelines
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({ name: 'page view', data: { 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' } },
},
},
},
});
Bundled (build from JSON config):
{
"version": 4,
"flows": {
"default": {
"config": {
"platform": "web",
"bundle": {
"packages": {
"@walkeros/collector": {},
"@walkeros/web-source-browser": {},
"@walkeros/web-destination-gtag": {}
}
}
},
"sources": {
"browser": {
"package": "@walkeros/web-source-browser",
"config": { "settings": { "pageview": true } }
}
},
"destinations": {
"ga4": {
"package": "@walkeros/web-destination-gtag",
"config": {
"settings": { "ga4": { "measurementId": "G-XXX" } }
}
}
}
}
}
}
Then: npx walkeros bundle flow.json
walkerOS exposes a Model Context Protocol (MCP) interface. AI agents can read your event schema, suggest tracking definitions, and generate integration code - making your event layer programmable, not just configurable.
In Claude Code, one plugin installs both MCP servers and the walkerOS skills:
/plugin marketplace add elbwalker/walkerOS
/plugin install walkeros@elbwalker
For any other MCP client, add the servers to its configuration:
{
"mcpServers": {
"walkeros-flow": {
"command": "npx",
"args": ["@walkeros/mcp"]
},
"walkeros-source-browser": {
"command": "npx",
"args": ["@walkeros/mcp-source-browser"]
}
}
}
Loading a flow, validating it, and simulating an event all run locally, no account needed. See the MCP docs.
Coming from Google Tag Manager? See walkerOS vs. GTM.
⭐️ Help us grow and star us. See our Contributing Guidelines to get involved.
Need help? Start a discussion, or reach out via email.
For more insights, visit the talks repository.
Licensed under the MIT License.
Build, validate, simulate, and deploy walkerOS event pipelines
{ "mcpServers": { "io.walkeros-flow": { "command": "npx", "args": [ "-y", "@walkeros/[email protected]" ], "env": { "WALKEROS_TOKEN": "<secret>", "WALKEROS_PROJECT_ID": "<value>", "WALKEROS_APP_URL": "<value>" } } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
El publicador indica estas variables de entorno: WALKEROS_TOKEN, WALKEROS_PROJECT_ID, WALKEROS_APP_URL.
WalkerOS Flow se ejecuta localmente por stdio.
Última comprobación: 2026-11-10. Build, validate, simulate, and deploy walkerOS event pipelines