tidemill

Command-line client for Tidemill — 33 free browser utility tools, no accounts, no cloud.

Tidemill has no accounts and no API keys. Every command below is public and read-only; there is no login.

npx tidemill list-tools
npx tidemill get-tool strobe-tuner
npx tidemill verify-license tm_...
npx tidemill search "pitch tuner"
npx tidemill fetch tool:strobe-tuner
npx tidemill remote                      # Zero Remote bridge (see below)

tidemill remote — control a Roku from the browser

Zero Remote is a browser tool, and a browser cannot talk to a Roku: ECP sends no CORS headers, discovery needs a UDP multicast socket no page has, and an https:// page may not reach a plain http:// device. tidemill remote is the half that can. Run it on the machine with the browser on it:

npx tidemill remote            # or: npx tidemill remote --port=8100

Then open https://tidemill.io/tools/zero-remote — it finds the bridge and takes over: every button is a real ECP keypress, "Find my Rokus" is real SSDP discovery, and the text field types a whole string to the Roku keyboard. If your browser refuses to talk to localhost from an https page (Safari does), the bridge serves the same remote itself at http://127.0.0.1:8099/.

No npm? The bridge is one file with no dependencies:

curl -fsSL https://tidemill.io/tidemill-remote.mjs -o tidemill-remote.mjs && node tidemill-remote.mjs

It binds 127.0.0.1 only, forwards only to private LAN addresses, accepts only the documented Roku ECP key names, and answers CORS for tidemill.io and localhost alone. Nothing it does leaves your network, and it stores nothing.

Add --json to any command for machine-readable output.

Set TIDEMILL_API_URL to point the CLI at a different deployment (defaults to https://tidemill.io).

Same API the MCP server (https://tidemill.io/mcp) and REST API (/api/v1, documented at /openapi.json) use — see tidemill.io/docs/agents for setup with Claude Code, claude.ai, Cursor, ChatGPT/Codex and more.