Revnu MCP Server

What is Revnu MCP Server?

The Revnu MCP server connects your AI assistant to Revnu, a hosted growth agent that finds buyers, runs outreach and ads, and writes SEO and AI-search pages. Through it, Claude, Cursor or VS Code can hand Revnu work, review what it wants to send, and read leads and results.

Revnu describes itself as "GTM on autopilot" for founders and small teams who have a product and want customers, users, leads, ads or SEO. The Revnu MCP endpoint is a remote Streamable HTTP server at https://revnu.com/api/mcp, so there is nothing to install locally. Signing in with OAuth connects your existing Revnu account, or creates one if you do not have an account yet.

How to use Revnu MCP Server?

You need an MCP client that supports remote servers and a browser to complete the sign-in. No API key is required for the remote connector: on first connect you sign in to Revnu and choose which permissions the app gets.

Server URL:

https://revnu.com/api/mcp

Claude Code

claude mcp add --transport http revnu https://revnu.com/api/mcp

Then run /mcp inside Claude Code and sign in to Revnu in the browser window that opens.

Claude Desktop

Open Settings, then Connectors, choose Add custom connector, paste https://revnu.com/api/mcp and click Connect. The same custom connector works on claude.ai.

Cursor

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "revnu": {
      "url": "https://revnu.com/api/mcp"
    }
  }
}

Cursor opens the Revnu sign-in in your browser when it first connects.

VS Code

Add the server to .vscode/mcp.json:

{
  "servers": {
    "revnu": {
      "type": "http",
      "url": "https://revnu.com/api/mcp"
    }
  }
}

Start the server from the MCP list and complete the OAuth sign-in in the browser.

Revnu also documents a ChatGPT connector (developer mode, OAuth), a CLI (npm install -g @revnu/cli) and a local MCP server (npx -y @revnu/cli mcp) that authenticates with a REVNU_API_TOKEN environment variable, for hosts that prefer a token over OAuth.

Key features of Revnu MCP Server

• Hosted remote server over Streamable HTTP; no local process for the standard setup.
• OAuth sign-in that creates a per-app API token, revocable under Settings, Developers in Revnu.
• Scoped access: each assistant sees only the tools its token's scopes allow (for example, a review:read token can only list and read cards).
• Approval-first sending: per Revnu, nothing goes out until you approve its card or have allowed that kind of work to ship on its own; replies in live conversations always wait for an explicit send.
• Covers the main Revnu surfaces documented by the vendor: the review queue, new jobs for the agent, results by channel, leads and labels, a block list, and recurring workflows.
• Onboarding from the assistant: accounts still in setup see setup tools such as setup_status, which returns the next setup step.
• Apps unused for 90 days are disconnected automatically.

Use cases of Revnu MCP Server

• Clearing the approval queue from your editor: "Show me the Revnu review cards waiting for me and summarize each draft."
• Handing off a growth task: "Ask Revnu to find 20 seed-stage fintech founders who might need our product."
• Lead triage: "List new Revnu leads from this week and label the ones that replied positively."
• Workflow control: "Pause the recurring LinkedIn outreach workflow until Monday."
• Reporting: "What results did Revnu get by channel this month?"
• Keeping contacts clean: "Add this address to the Revnu block list."

Troubleshooting Revnu MCP Server

• Tools are missing. The tool list depends on the scopes granted to the app's token. Reconnect and grant the permissions you need, or check the token under Settings, Developers.
• The connection stopped working. Revnu disconnects apps that have not been used for 90 days. Reconnect to get a new token.
• Only setup tools appear. Accounts that have not finished onboarding see setup_* tools first; call setup_status to see the next step.
• Your host cannot do OAuth. Use the local server via npx -y @revnu/cli mcp with REVNU_API_TOKEN, or send a bearer token created under Settings, Developers.