RevenueCat MCP Server

What it does

RevenueCat runs this server itself at https://mcp.revenuecat.ai/mcp. It wraps the RevenueCat API v2 so an assistant can do work you would otherwise do in the RevenueCat dashboard: create and edit apps, products, entitlements, offerings and packages, set targeting rules and audiences, build and publish paywalls, look up customers and their subscriptions, and read charts, headline metrics and experiment results.

It also reaches past RevenueCat into the app stores. A set of product store state tools reads and changes product prices, availability and review details in App Store Connect and Google Play Console through a draft, plan and apply cycle, and can submit App Store products for review. Paywalls can be generated or edited by RevenueCat's own paywall AI editor as background tasks, and rendered to a PNG to check the result.

The tools reference lists 117 tools: 57 that only read and 60 that create, change or delete something. The server hides tools the sign-in does not allow, so a read-only key or a read-only OAuth grant shows only the read tools. The endpoint's sign-in metadata names exactly two scopes, *:*:read and *:*:read_write, so access is chosen as read or read-write rather than per resource. RevenueCat also offers an AI Toolkit plugin for Claude Code, Codex and Cursor that installs this same server plus workflow skills; this page covers the server on its own.

What it needs

A RevenueCat account with at least one project. Sign in either with OAuth (Claude, Codex, Copilot, Cursor, VS Code and some other clients) or with a RevenueCat API v2 secret key sent as a Bearer header, which every client can use. A write-enabled key or read-write grant is needed for any change. Codex needs `codex mcp login revenuecat` after adding the server. Store product tools need the store credentials set up in RevenueCat; for Google Play the service account needs the Manage store presence permission. Claude Team and Enterprise need an Owner to add the custom connector first.

Limits

Hosted only: there is no package or source to run yourself. Four tools are marked deprecated in the reference: create-product-prices, equalize-subscription-prices, set-product-store-state and get-product-store-state-operation. OAuth works only for clients RevenueCat has allowlisted; others fail with an unknown-client error until RevenueCat support adds them, and changed redirect URIs can break sign-in the same way. The reference covers the generally available tools and RevenueCat says the set changes over time, so the client's tool list is what counts. There is no tool to delete an app, product or entitlement; archive tools are offered instead.

Who it suits

Teams that already run in-app subscriptions on RevenueCat and want an assistant to set up products, offerings, paywalls and experiments, or to pull metrics and customer records, without opening the dashboard. Being official and hosted, nothing runs on your machine. Because many tools change live store listings, prices and what customers see, start with a read-only key or grant and move to read-write only for setup work. Developers using Claude Code, Codex or Cursor who also want guided workflows may prefer RevenueCat's AI Toolkit plugin, which installs this server for them.