@revnu/cli

Your revnu growth agent from the command line, and as an MCP server for Claude Desktop, Claude Code and Cursor.

revnu is the growth hire for your business. It drafts outreach, writes and publishes content, runs ads and reports what worked, and puts anything that needs your say-so in a review queue. This package lets your own software, or your own AI assistant, read that queue, approve or decline cards, message the agent, and pull results.

Full API reference: https://revnu.com/guides/revnu-api

Install

npm install -g @revnu/cli
revnu auth login          # paste a personal token from revnu.com → settings → API tokens

Or skip the login and set REVNU_API_TOKEN in the environment. Tokens start with rvp_, are shown once when minted, and carry only the scopes you picked (review:read, review:write, agent:message, results:read, leads:read).

As an MCP server

Add to Claude Desktop (claude_desktop_config.json), Claude Code (claude mcp add revnu -- npx -y @revnu/cli mcp), or Cursor:

{
  "mcpServers": {
    "revnu": {
      "command": "npx",
      "args": ["-y", "@revnu/cli", "mcp"],
      "env": { "REVNU_API_TOKEN": "rvp_..." }
    }
  }
}

Tools, one per API route: whoami, review_list, review_get, review_answer, review_send, review_request_changes, review_snooze, review_dismiss, agent_message (posts, then waits for the reply), agent_message_status, agent_thread, agent_status, results_get, workflows_list, workflow_runs, leads_list, lead_get.

Writes are real: review_answer on a blog draft publishes it, review_send sends email from your mailbox. Mint a read-only token if your assistant should only look.

As a CLI

revnu whoami
revnu review list
revnu review approve <id>
revnu review request-changes <id> --text "Shorter, and lead with the case study."
revnu agent message "What did we ship this week?" --wait 90
revnu results --since 2026-09-01
revnu leads list --status replied

Every whoami, review, agent, results, workflows and leads command prints JSON to stdout, so | jq works; help, version and auth login print text, and revnu mcp speaks JSON-RPC. Exit codes: 0 ok, 1 the API said no, 2 usage.

Configuration

| Variable | Meaning | |---|---| | REVNU_API_TOKEN | personal token, overrides the saved config | | REVNU_API_BASE | API base, default https://revnu.com/api/v1 | | XDG_CONFIG_HOME | where revnu/config.json lives, default ~/.config |

The saved config file is mode 600 and holds the token in plain text. revnu auth logout deletes it.