eventfy-cli

Command-line tools for Eventfy — forward live webhooks to your own machine, replay saved test suites in CI, and let an AI assistant drive Eventfy over MCP.

Zero dependencies. Plain Node, works anywhere Node 18+ runs.

Install

npm install -g eventfy-cli

Or run it without installing:

npx eventfy-cli listen 3000 --server https://www.eventfy.space --lens <lens-token>

Forward webhooks to your machine

You need your local app running, and the port it listens on — that's the number in the address you open in your browser. If it's http://localhost:3000, your port is 3000.

eventfy listen 3000 --server https://www.eventfy.space --lens <lens-token>

Your lens token is on the Webhooks page in the dashboard, already filled into the command there — copy it from the app rather than typing it out.

Leave it running while you work. Nothing on your machine is exposed to the internet: the CLI opens an outbound connection to Eventfy and pushes what arrives to your local port.

Replay a test suite in CI

eventfy run-suite <suite-id> --target <target-id> --server https://www.eventfy.space --key <api-key>

Exits non-zero if any request in the suite fails, so it works as a CI gate. Your API key is on the Webhooks page under step 3 — keep it private.

Use with an AI assistant (Pro and above)

eventfy-mcp is an MCP server. It lets Claude Desktop, Claude Code, or any MCP-capable assistant create webhook URLs, read caught events, re-fire them, and build flows.

eventfy-mcp --key <api-key>

In Claude Desktop, add it to claude_desktop_config.json:

{
  "mcpServers": {
    "eventfy": {
      "command": "eventfy-mcp",
      "args": ["--key", "<your-api-key>"]
    }
  }
}

Every tool calls the same API the dashboard uses, with your workspace API key — so it can do exactly what a person holding that key could do, and no more. The key is scoped to one workspace: it cannot switch workspaces, read another workspace's data, or touch billing.

Full documentation

https://www.eventfy.space/docs