RevenueCat MCP Server

The RevenueCat MCP Server is the official Model Context Protocol server from RevenueCat, the leading provider of in-app subscription infrastructure. It is operated by RevenueCat itself and offered exclusively as a hosted service at https://mcp.revenuecat.ai/mcp, making it a remote MCP server with no local installation. It connects MCP-capable AI assistants — according to the provider these include Claude, Claude Code, Codex, Cursor, and ChatGPT — directly to a RevenueCat project, so subscription configurations, products, entitlements, and customer data can be queried and updated from the chat instead of switching back and forth between the assistant and the RevenueCat dashboard. RevenueCat officially announced the server in July 2026.

What is RevenueCat?

RevenueCat is a specialized platform that provides developers with a unified API for in-app purchases and subscriptions across the App Store (Apple), Google Play, and Stripe. Its core capabilities include subscription lifecycle management, entitlement checks, paywall logic, and revenue analytics. According to the provider, RevenueCat processes billions of transactions per year for tens of thousands of apps worldwide. The MCP server makes this infrastructure directly accessible from AI assistants.

Prerequisites and API Key

To use the RevenueCat MCP Server, an existing RevenueCat account is required. The MCP server supports two authentication methods: either an API v2 secret key (Bearer token) created in the project settings under the "API keys" tab, or OAuth for clients that support the OAuth protocol, including Claude, Claude Code, Codex, Cursor, VS Code, and GitHub Copilot. The API key must have at least the read permissions needed for the given project; write actions such as creating products or offerings require extended write permissions. This catalog entry deliberately states no concrete prices; the official RevenueCat pricing page is authoritative.

Features: Subscriptions, Products, Entitlements, and Customers

According to the provider, the MCP server exposes tools for the following task areas:

Project management: Retrieve and overview RevenueCat project details, including all associated apps.

App management: Create, read, update, and delete apps across all supported platforms (iOS, Android, Stripe, and others).

Product and product catalog management: Manage subscription products and in-app purchases; inspect and change prices, availability, and review metadata directly in App Store Connect and Google Play Console, without opening the respective store dashboard.

Offering and package management: Create and maintain RevenueCat Offerings and the Packages within them, which control the app's paywall logic.

Entitlements: Check and configure entitlements — the access-gated content levels that determine which app features a user receives after a purchase.

AI-assisted paywall creation: Create and update RevenueCat Paywalls through an AI assistant, currently via the Rico tool.

Analytics and experiments: Retrieve and analyze charts as well as A/B experiment results directly in the chat, without opening the RevenueCat dashboard.

Setup

The recommended setup for AI coding assistants (Claude Code, Codex, Cursor) is the RevenueCat AI Toolkit — a plugin that automatically installs and configures the MCP server and also includes pre-built workflows (skills). For a manual setup there are two paths:
Claude Code: claude mcp add --transport http revenuecat https://mcp.revenuecat.ai/mcp --header "Authorization: Bearer YOUR_API_V2_SECRET_KEY"
Cursor, VS Code, claude.ai: Add the remote endpoint https://mcp.revenuecat.ai/mcp in the MCP client and either choose OAuth or store the Bearer token as an Authorization header.
Clients without native remote support: use the bridge npx mcp-remote https://mcp.revenuecat.ai/mcp --header "Authorization: Bearer YOUR_API_V2_SECRET_KEY".

RevenueCat provides detailed step-by-step guides for all supported clients in its official documentation.

Security and Privacy

The connection to the MCP server is authorized per user via OAuth or API key Bearer token; in both cases the AI assistant acts within the permission scope of the API key's rights. Write actions — such as creating or modifying products, offerings, or entitlements — should be reviewed before they run because they take effect directly in the app's production configuration. RevenueCat recommends using dedicated API keys with a minimal permission profile for the AI connection and avoiding project owner keys. Since the server is hosted by RevenueCat, tool calls land on RevenueCat infrastructure; RevenueCat's privacy policy is authoritative. Customer data (app users) can be retrieved through the server to the extent the API key permissions allow; sensitive customer data should be retrieved with care.

Who benefits from it?

The RevenueCat MCP Server is aimed primarily at app developers who already use RevenueCat for their subscription management and have integrated AI assistants such as Claude, Cursor, or Codex into their development workflow. Typical use cases per the provider are: configuring products and offerings without opening the dashboard; checking and adjusting entitlements; iteratively improving paywalls through an AI assistant; evaluating experiment results. Developers who do not yet use RevenueCat first need to complete the basic RevenueCat account setup before they can benefit.

FAQ

Do I need to self-host the server? No. RevenueCat operates it fully hosted at https://mcp.revenuecat.ai/mcp. There is no public repository for operating the server; only the AI Toolkit plugin is open source.

Which RevenueCat plan is required? According to the provider, the MCP server is available for all RevenueCat accounts, including the free starter plan. Feature scope and API limits follow the subscribed plan; concrete amounts are only on the official pricing page.

Can the server retrieve customer data of my app users? Yes, depending on the permissions of the API key in use, customer data can be viewed. Dedicated keys with a minimal permission profile are recommended.

A RevenueCat account and either an API v2 secret key or an OAuth-capable MCP client. Clients without native remote support need Node.js for the mcp-remote bridge.

Add the remote endpoint https://mcp.revenuecat.ai/mcp in the MCP client and sign in via OAuth or store the Bearer token as an Authorization header. Claude Code: claude mcp add --transport http revenuecat https://mcp.revenuecat.ai/mcp --header "Authorization: Bearer YOUR_KEY". Alternatively install the RevenueCat AI Toolkit, which automates setup and adds skills.

npx mcp-remote https://mcp.revenuecat.ai/mcp

Bearer token with a RevenueCat API v2 secret key, or OAuth. OAuth is supported for Claude, Claude Code, Codex, Cursor, VS Code, and GitHub Copilot.

The agent acts within the permission scope of the API key in use. Read permissions suffice for queries; write actions (creating/modifying products, offerings, entitlements) require extended write permissions. Recommended: dedicated keys with a minimal permission profile.

Tool calls run through the RevenueCat API on RevenueCat infrastructure. App user customer data can be retrieved depending on key permissions. RevenueCat's privacy policy is authoritative.

Write actions take effect directly on the app's production configuration (products, offerings, entitlements). Review before running. Do not use project owner keys for the AI connection; instead use dedicated keys with a minimal permission profile.