npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@waterfallbridge/mcp

v1.2.4

Published

Explain why any KPI or rate metric changed. An MCP server that runs deterministic bridge/waterfall variance analysis on CSV or Excel data — decomposing the change (including percentages and ratio metrics) by dimension and driver, with contribution analysi

Readme

@waterfallbridge/mcp

MCP (Model Context Protocol) server for WaterfallBridge — lets AI hosts such as Cursor, Codex CLI, and Claude Desktop prepare data, run waterfall / bridge variance analysis, and read results by driving the WaterfallBridge web app through Playwright.

This is the same code that ships inside the WaterfallBridge-Agent.exe desktop installer — only the packaging differs. The npm package targets users who already have Node.js and want a one-line, registry-friendly install; the EXE targets users who want a self-contained download with bundled Chromium and a system tray.

What it does

The server exposes a single tool suite over two transports:

  • stdio MCP — spawned by an MCP host (Cursor / Codex / Claude Desktop).
  • local HTTP / WebSocket — used by the in-app AI panel (optional).

Tools include open_app, login, upload_file, run_bridge, get_chart_data, prepare_bridge_xlsx, and a local-filesystem suite for AI-assisted data preparation. See the AI Integration Guide for the full reference.

Account required. Running analyses needs a WaterfallBridge account and an active subscription (server-side formulaBreakdown is subscription-gated).

Requirements

  • Node.js >= 18

  • Chromium — installed automatically on first launch via playwright install chromium (~150 MB, one time). You can also pre-install it manually:

    npx playwright install chromium

Use it from an MCP host

Cursor — ~/.cursor/mcp.json (or project .cursor/mcp.json)

{
  "mcpServers": {
    "waterfall-bridge": {
      "command": "npx",
      "args": ["-y", "@waterfallbridge/mcp", "--mode=stdio"],
      "env": { "WB_HEADLESS": "false" }
    }
  }
}

Codex CLI — ~/.codex/mcp.json

{
  "mcpServers": {
    "waterfall-bridge": {
      "command": "npx",
      "args": ["-y", "@waterfallbridge/mcp", "--mode=stdio"],
      "env": { "WB_HEADLESS": "false" }
    }
  }
}

Claude Desktop — claude_desktop_config.json

Same mcpServers block as above. On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json; on macOS at ~/Library/Application Support/Claude/claude_desktop_config.json.

Run directly

# stdio MCP server (what MCP hosts spawn)
npx -y @waterfallbridge/mcp --mode=stdio

# local HTTP/WS server (in-app AI panel, default port 39871)
npx -y @waterfallbridge/mcp --mode=local

Environment variables (common)

| Variable | Default | Purpose | |-------------------|----------------------------------------|-------------------------------------------| | WB_DEFAULT_URL | https://waterfallbridge.com/app/ | URL open_app opens when none is passed | | WB_HEADLESS | false (dev) / true (prod) | Run the automation Chromium headless | | WB_PORT | 39871 | Local HTTP/WS port (--mode=local) | | WB_DATA_DIR | OS-specific | Where sessions / credentials are stored |

The full list (filesystem allow-list, auth token, external MCP config, …) is documented in the project's AGENT_ARCHITECTURE.md.

License

MIT — see LICENSE.