waterfallbridge MCP

waterfallbridge MCP runs locally from a Node.js package published to the npm registry: @waterfallbridge/mcp version 1.2.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @waterfallbridge/mcp@1.2.4. It reads these environment variables: WB_DEFAULT_URL and WB_HEADLESS; set them in the client's configuration for this server. Required arguments: --mode=stdio.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@waterfallbridge/mcp@1.2.4"
      ],
      "env": {
        "WB_DEFAULT_URL": "<value>",
        "WB_HEADLESS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect