walkerOS Flow MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token';

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const destPath = path.join(outputDir, folderName);

        dom.window.eval(snapshotCode);

    path.join(homeDir, '.npmrc'),

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add flow -- npx -y @walkeros/mcp

{
  "mcpServers": {
    "flow": {
      "args": [
        "-y",
        "@walkeros/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.flow]
command = "npx"
args = ["-y", "@walkeros/mcp"]

{
  "mcpServers": {
    "flow": {
      "args": [
        "-y",
        "@walkeros/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "flow": {
      "args": [
        "-y",
        "@walkeros/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: WALKEROS_TOKEN (walkerOS 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.). The author declared them in the registry entry; get the values from the project itself.