The AI Toolkit is distributed as a plugin marketplace from a single GitHub repository: RevenueCat/ai-toolkit. It ships two plugins.

The RevenueCat Plugin

This is the one most users want. It combines two things:

The RevenueCat MCP server is a hosted Model Context Protocol server at mcp.revenuecat.ai that gives your agent authenticated access to your RevenueCat account. Through it, the agent can create and inspect projects, apps, products, entitlements, offerings, and packages, and query your analytics data.

Cross-platform integration skills are curated, versioned instructions that teach your agent how to do common RevenueCat tasks the right way on iOS, Android, Kotlin Multiplatform, Flutter, and React Native:

• integrate-revenuecat: end-to-end integration that sets up the dashboard side via the MCP and installs/configures the Purchases SDK in your app.
• create-revenuecat-project: sets up a complete project from scratch: apps, products, entitlements, offerings, and packages in the correct order.
• revenuecat-paywall: displays a paywall using the RevenueCatUI SDK.
• revenuecat-purchase-flow: implements purchasing, error handling, and restore.
• revenuecat-entitlements-gate: gates premium features behind entitlements.
• revenuecat-identify-user: ties RevenueCat identity to your app's auth system.
• revenuecat-customer-center: adds the self-service subscription management UI.
• revenuecat-testing-setup: sets up sandbox/test environments so you can test without spending real money.
• revenuecat-troubleshoot: diagnoses integration issues using dashboard config and SDK debug logs.
• revenuecat-migrate: migrates from raw StoreKit or Play Billing, or across SDK major versions.
• revenuecat-status: quick overview of your project configuration.
• revenuecat-charts: answers questions about your data, analytics, and KPIs.

The revenuecat-play-billing Plugin

An optional second plugin with 20 deep Google Play skills for the RevenueCat Android SDK, with handbook-level coverage of the Google Play subscription lifecycle: purchases, plan and price changes, payment recovery, pauses and cancellations, win-back, webhooks, security, and more. It's synced from RevenueCat/play-billing-skills, which is the source of truth.

Tip: Start with the RevenueCat plugin. Add revenuecat-play-billing on top if you ship Android and want handbook-level depth on Google Play billing behavior.

Claude Code supports plugin marketplaces natively, so installation takes under a minute. There are two ways to do it.

From Within Claude Code

Start Claude Code in your project and run:

/plugin

Then select Marketplace → + Add Marketplace, and enter RevenueCat/ai-toolkit. Once the marketplace is added, select the RevenueCat plugin to install it. If you ship Android and want handbook-level Google Play depth, also select revenuecat-play-billing.

From the Command Line

Prefer the terminal? The same thing in three commands:

claude plugins marketplace add RevenueCat/ai-toolkit
claude plugins install RevenueCat
claude plugins install revenuecat-play-billing

That's it. The plugin registers the RevenueCat MCP server and makes all the skills available to Claude. You can verify the installation by typing / in Claude Code. You should see the RevenueCat skills (like /revenuecat-status) in the command list.

The toolkit works across the major AI coding environments. Pick yours below.

OpenAI Codex CLI

codex plugin marketplace add RevenueCat/ai-toolkit

Then start Codex, run /plugins, search for RevenueCat, and install. For the Codex desktop app, run the same terminal command first, then click Plugins in the app, select RevenueCat from the dropdown, and click the + button next to the plugin.

Gemini CLI

gemini extensions install https://github.com/RevenueCat/ai-toolkit

Gemini has no marketplace and supports a single extension per repository, so it installs the RevenueCat plugin only. The revenuecat-play-billing plugin is available on Claude Code, Cursor, Codex, and VS Code.

Visual Studio Code

Plugin marketplace support is currently in beta in VS Code. Follow the official instructions to add RevenueCat/ai-toolkit as a plugin marketplace, then install the plugin from the marketplace.

Cursor

Marketplace support is coming soon. In the meantime, you can add the RevenueCat MCP server directly to get the dashboard tools.

Any Other Agent

For agentic coding environments without plugin support, you can install just the skills with npx:

npx skills add RevenueCat/ai-toolkit

Note: this installs only the skills, not the MCP server. Configure the MCP manually in your environment by following the MCP setup instructions.

The MCP server needs to act on your RevenueCat account, so it authenticates via OAuth in your browser. No API keys to copy around. Access is granted based on your RevenueCat account permissions and covers all your projects.

When the authentication prompt appears depends on your environment:

• Immediately: some environments prompt you to authenticate as soon as the plugin is installed.
• On first use: others wait until the agent first calls a RevenueCat tool.
• Manually: in Gemini CLI, run /mcp auth revenuecat to kick off the flow yourself.

In every case the flow is the same: your browser opens, you sign in to RevenueCat (if you aren't already), and approve the access request. Once that's done, your agent is connected.

A quick way to verify everything works end-to-end is to ask for a project status:

You: What is the status of my RevenueCat project?

Agent: RevenueCat Project Status
       ============================
       Project: Fitness App (proj123)

       Apps: 2 (iOS, Android)
       Products: 4
       Entitlements: 2
       Offerings: 1

       ✅ Configuration looks healthy!

If you see a summary like this, authentication succeeded and the MCP connection is live. If you don't have a project yet, don't worry. You'll create one in the next step.

Note: The toolkit can read and modify your real RevenueCat configuration. Review what your agent proposes before approving changes, exactly as you would with code.

This is where the toolkit shines. Setting up RevenueCat traditionally means clicking through the dashboard to create apps, products, entitlements, offerings, and packages (in the right order) and then wiring up the SDK in your code. With the toolkit installed, you describe the outcome and the agent does both sides.

Create the Dashboard Configuration

Start with a prompt like this in your project:

You: Set up RevenueCat for my fitness app

Agent: I'll help you set up RevenueCat. What platforms are you building for?

You: iOS and Android

Agent: Creating your iOS app... [creates app]
       Creating your Android app... [creates app]
       What subscription tiers do you want? (e.g., monthly, annual)

You: Monthly at $9.99 and annual at $79.99

Agent: [Creates products, entitlements, offering, packages]

       Setup complete! Here are your API keys:
       iOS: appl_xxxxx
       Android: goog_xxxxx

Behind the scenes, the create-revenuecat-project skill drives the MCP server to create everything in the correct dependency order: apps first, then products, then an entitlement (like premium) attached to those products, then an offering with monthly and annual packages. These are real resources in your RevenueCat dashboard. Open it in the browser and you'll see them.

Integrate the SDK

If you're working inside an existing app codebase, use the end-to-end integration skill instead. It handles the dashboard side and installs and configures the Purchases SDK in your project:

You: Integrate RevenueCat into this app

The integrate-revenuecat skill detects your platform (iOS, Android, KMP, Flutter, or React Native), adds the SDK dependency, fetches the correct public API key from your project via the MCP, and configures Purchases at app launch following best practices, the same patterns taught in the platform codelabs on this site.

Tip: When you're done, run /revenuecat-status (or just ask "what's my project status?") to confirm apps, products, entitlements, and offerings are all in place.

With the project configured, the integration skills help your agent build each monetization feature the right way. You don't need to invoke skills by name. They activate automatically when your request matches. Here are the prompts that trigger each one:

Show a Paywall

You: Gate the premium analytics screen behind a paywall

The revenuecat-paywall skill wires up the RevenueCatUI SDK: PaywallView on iOS, PaywallActivity or paywall composables on Android, presentPaywallIfNeeded where appropriate, using the paywall you configured in the dashboard's Paywall Editor.

Purchases, Restore, and Entitlement Gates

Asking for purchase logic, such as "implement the purchase flow for the annual package, with restore", activates revenuecat-purchase-flow, which fetches offerings, purchases packages, handles user cancellation and errors, and implements restore. Asking "only show this feature to subscribers" activates revenuecat-entitlements-gate, which checks active entitlements from CustomerInfo and reacts to entitlement changes.

Identity and the Customer Center

When you connect RevenueCat to your auth system, for example "sync RevenueCat with my Firebase Auth user on login and logout", the revenuecat-identify-user skill handles logIn/logOut and anonymous-to-identified transitions. And "add a manage subscription screen" activates revenuecat-customer-center to embed the self-service Customer Center UI.

Test Without Spending Money

You: How do I test purchases without real money?

The revenuecat-testing-setup skill walks your agent through the sandbox setup for your platform: StoreKit configuration files and sandbox accounts on iOS, license testers and internal testing tracks on Android, so you can exercise the full purchase flow safely. (For an even faster start, see the Test Store for iOS and Test Store for Android codelabs.)

The toolkit isn't just for setup. It stays useful for the day-to-day of running a subscription business.

Ask Questions About Your Data

The revenuecat-charts skill turns your agent into an analytics console. Ask things like "What's my MRR?", "How did trial conversion change after the last price test?", or "Show me churn for the past quarter" and the agent queries your real charts data through the MCP server and summarizes the answer.

Troubleshoot Conversationally

When something's off (empty offerings, an entitlement that isn't active after purchase, a paywall that won't load), describe the symptom:

You: My offerings are coming back empty on Android

The revenuecat-troubleshoot skill inspects your dashboard configuration through the MCP, walks the SDK debug logs, and checks the usual code-side gotchas. It's the same methodology as the Troubleshooting codelab, but executed by your agent against your actual project.

Migrations and Upgrades

Already have raw StoreKit or Google Play Billing code? "Migrate this app to RevenueCat" activates revenuecat-migrate, which also covers observer mode and major SDK version upgrades (like v4 → v5).

Go Deep on Google Play

If you installed revenuecat-play-billing, your agent gains 20 handbook-level skills on the Google Play subscription lifecycle: subscription states, plan changes, price changes, payment recovery, cancellations and pauses, win-back, one-time products, webhooks, security, and more. Ask "what happens to a subscription in grace period?" or "how do I handle a downgrade at renewal?" and the answers come from RevenueCat's curated Play Billing knowledge rather than the open web.

Congratulations! You've installed the RevenueCat AI Toolkit, authenticated with your account, set up a complete RevenueCat project from a single prompt, and learned how the skills help your agent build paywalls, purchase flows, entitlement gates, and the Customer Center, plus analyzing your data and troubleshoot issues, all without leaving your AI coding agent.

The toolkit turns RevenueCat's best practices into something your agent applies automatically. You stay in flow; the configuration, the boilerplate, and the institutional knowledge come to you.

Next Steps

To go deeper on any platform, pair the toolkit with the hands-on codelabs: iOS, Android, Kotlin Multiplatform, Flutter, and React Native. For the MCP server itself, see the MCP documentation.

You can also learn more through the resources below:

• GitHub: RevenueCat AI Toolkit
• Documentation: RevenueCat MCP Server
• GitHub: Play Billing Skills
• Product Tutorials: Video tutorials to help you get started and get the most out of RevenueCat.

Now go ship something amazing, and let your agent handle the busywork! 🤖💰