Revnu

com.revnuPublished by revnu.comOfficial publisherv1.10.6Updated Nov 12, 2026

GTM on autopilot. Revnu runs your pipeline, ads and GEO.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Revnu is a go-to-market automation service whose MCP endpoint lets an assistant work with your pipeline, ads and GEO from Revnu.

What you can do
  • No tools are listed in the manifest, so capabilities are known only from the description.
  • Revnu describes itself as running go-to-market work on autopilot: pipeline, ads and GEO.
  • An assistant connected to it would act on that Revnu account rather than on local files or data.
When to use it
Consider it if you already use Revnu for go-to-market execution and want an assistant to reach that account directly instead of switching to the Revnu interface.
Requirements
A Revnu account with OAuth sign-in, or a Revnu API token supplied as REVNU_API_TOKEN (from Settings → Developers); the token can be left unset after running the revnu login command. Available as a remote endpoint or as the local npm package @revnu/cli over stdio.
Before you install
The server requires OAuth and can also take an API token, so treat REVNU_API_TOKEN as a credential and keep it out of shared configuration. Because it automates pipeline and ad work, connected tools may change campaigns or pipeline data in your account; review what it can write before enabling it. No tool list is published, so verify permissions after connecting.

Installation

In SourceWeft

  1. Open Revnu in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.revnu%2Frevnu/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

5
  1. v1.10.6LatestNov 12, 2026
  2. v1.10.5Nov 11, 2026
  3. v1.10.3Nov 5, 2026
  4. v1.10.2Nov 4, 2026
  5. v1.3.0Sep 30, 2026

Score

65% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.