RevenueHogdocs
AI and MCP

AI and MCP

Ask Claude, Cursor or any MCP client about your revenue, subscriptions, reviews, feedback and payouts through the RevenueHog MCP server and Claude skills.

RevenueHog exposes your workspace's data to AI assistants through a Model Context Protocol (MCP) server, and ships a Claude Code plugin with four skills that know how to use it. An assistant connected to RevenueHog can answer questions like "how is my MRR doing", "which app has the best ROAS" or "what are users saying in reviews" from your real numbers.

What is included

PieceWhat it isWhere it lives
MCP serverA streamable HTTP MCP endpoint with eight rh_* tools over your workspace's data.https://revenuehog.dev/api/mcp
OAuth 2.1Sign-in flow for clients that support remote connectors (claude.ai, Claude Desktop, Cursor, VS Code)./oauth/authorize, /oauth/token, /oauth/register
MCP tokensPersonal access tokens shaped rh_mcp_... for headless clients (Claude Code, Codex, CI).Dashboard, Settings → MCP
Claude Code pluginA plugin named revenuehog that bundles the MCP connector and four skills.The Parra-Inc/revenue-hog plugin marketplace
Skillsrevenuehog-insights, revenuehog-integration, revenuehog-experiments, revenuehog-paywall.Installed with the plugin, or copied by hand

What the MCP server can do

Six tools read data and two manage feedback API keys:

  • rh_query computes metrics (proceeds, MRR, churn rate, ROAS and 27 more) over a time window, optionally broken down by app, country, product or campaign.
  • rh_meta describes the metric catalog, gives a formula for every metric, and reports how fresh each data pipeline is.
  • rh_reviews reads mirrored App Store reviews.
  • rh_feedback reads in-app feedback (bug reports, ideas, questions, praise).
  • rh_experiment_results lists paywall A/B experiments and returns per-variant results.
  • rh_payouts lists Apple payout periods and the next expected payment.
  • rh_create_api_key mints a server-to-server feedback API key and returns its secret once.
  • rh_list_api_keys lists existing feedback API keys without secrets.

Every tool is scoped to exactly one workspace: the one the token or connection was issued for. None of the tools change your revenue data, apps or settings. The only write is creating a feedback API key.

The MCP tab may be hidden

The MCP tab in Settings is controlled by a feature flag. If you do not see it, open /settings/mcp on the dashboard directly; the page works either way.

Where to start

Last updated on

On this page