Hosted MCP server/Marketing

Revnu MCP server

Hosted at revnu.com·Streamable HTTP

Revnu lets an agent review growth work, browse leads and results, message the AI growth agent, and schedule workflows. Setup uses npx -y @revnu/cli setup agent, then browser sign-in through revnu login or a REVNU_API_TOKEN from /docs/authentication. Token scopes are visible with revnu whoami. The CLI requires macOS, Linux, or WSL; native Windows users need the Revnu plugin.

revnu.com Streamable HTTP Browser sign-in with REVNU_API_TOKEN; scopes visible in revnu whoami Server not checked yet Reviewed 2026-11-16
About

Where it fits

Growth teams and founders who review campaign work, leads, and scheduled workflows through an AI growth agent.

  • Run the Revnu CLI setup and sign in.
  • Review recent growth work and results.
  • Schedule a workflow with the AI growth agent.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Provider CLI setup

Requires macOS, Linux, or WSL. Native Windows users need the Revnu plugin at https://github.com/revnu-app/revnu-plugin#install. Then run revnu login or set REVNU_API_TOKEN. Token scopes are visible with revnu whoami.

  1. Run the setup

    The CLI writes the MCP configuration for supported clients.

    npx -y @revnu/cli setup agent
  2. Sign in

    Use the browser sign-in or set REVNU_API_TOKEN from the provider's authentication docs.

    revnu login
  3. Check scopes

    Review the token scopes before running growth workflows.

    revnu whoami

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://revnu.com/api/mcp
Host
revnu.com · /api/mcp
Transport
Streamable HTTP
Authentication
Browser sign-in with REVNU_API_TOKEN; scopes visible in revnu whoami
Server name
revnu
Listing type
Community or directory listing

The installer uses the server name revnu. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that revnu appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Run the Revnu CLI setup and sign in. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Revnu documentationhttps://revnu.com/docs/cli