Connect an MCP client

Any MCP client that supports remote servers over streamable HTTP can connect to RevenueHog. Clients with OAuth support sign you in through the browser. Others use an MCP token in an Authorization header.

Before you startCopy Anchor Link

• A RevenueHog account with at least one connected app, so there is data to read.
• The server URL: https://revenuehog.dev/api/mcp.
• For headless clients, an MCP token from Settings → MCP. See MCP tokens.
• Make sure the workspace you want is active. Both OAuth connections and MCP tokens are bound to one workspace.

Pick a methodCopy Anchor Link

claude.ai and Claude DesktopCopy Anchor Link

On Team and Enterprise plans, an owner may need to add the connector for the organization first.

CursorCopy Anchor Link

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

{
  "mcpServers": {
    "revenuehog": {
      "url": "https://revenuehog.dev/api/mcp"
    }
  }
}

Check Cursor Settings → MCP for a green status and eight rh_* tools.

VS CodeCopy Anchor Link

{
  "servers": {
    "revenuehog": {
      "type": "http",
      "url": "https://revenuehog.dev/api/mcp"
    }
  }
}

VS Code runs OAuth when the server first starts. To use a token instead, add "headers": { "Authorization": "Bearer ${input:revenuehog-token}" } and declare a password input so the token is not stored in the file.

Claude CodeCopy Anchor Link

claude mcp add --transport http revenuehog https://revenuehog.dev/api/mcp \
  --header "Authorization: Bearer $REVENUEHOG_MCP_TOKEN"

Run /mcp in a session to confirm it is connected. Installing the RevenueHog plugin also adds the server; see Claude Code.

Codex CLICopy Anchor Link

[mcp_servers.revenuehog]
url = "https://revenuehog.dev/api/mcp"
bearer_token_env_var = "REVENUEHOG_MCP_TOKEN"

Export REVENUEHOG_MCP_TOKEN in the shell that runs Codex.

Other clientsCopy Anchor Link

Any client works if it can:

1. Send JSON-RPC over HTTP POST to https://revenuehog.dev/api/mcp.
2. Either run OAuth 2.1 with PKCE (S256) and dynamic client registration, or send a static Authorization: Bearer rh_mcp_... header.

Clients that only support local stdio servers can use a stdio-to-HTTP bridge such as mcp-remote:

{
  "mcpServers": {
    "revenuehog": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://revenuehog.dev/api/mcp",
               "--header", "Authorization: Bearer ${REVENUEHOG_MCP_TOKEN}"],
      "env": { "REVENUEHOG_MCP_TOKEN": "rh_mcp_..." }
    }
  }
}

Verify the connectionCopy Anchor Link

Ask your assistant to call rh_meta with topic freshness. A working connection returns the newest data date for revenue, subscriptions and ads, plus the last sync run. An MCP token shows a recent used time in Settings → MCP.

TroubleshootingCopy Anchor Link

RelatedCopy Anchor Link