RevenueCat AI Toolkit
Plugins, skills, an MCP server, and a CLI that let your coding agent work with RevenueCat
The RevenueCat AI Toolkit is what you install so your own coding agent can work with RevenueCat. It gives your agent both halves of what it needs: a connection to your RevenueCat projects, and the knowledge to use that connection correctly.
The toolkit has four parts.
| Part | What it gives you |
|---|---|
| Plugins | One install that sets up the skills and the MCP server for your assistant. |
| Skills | Playbooks that give your agent the right order of operations for a RevenueCat workflow. |
| MCP Server | A live connection between your agent and your RevenueCat projects. |
| CLI | Commands for setup, credentials, and project configuration from your terminal or an agent. |
Most people should start with a plugin. It installs the skills and configures the MCP server for you, so the other pages matter only if you want to set something up on its own.
What you can ask your agent to do
- Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages
- Integrate the Purchases SDK on iOS, Android, Kotlin Multiplatform, Flutter, or React Native
- Build and customize Paywalls
- Manage store product state: prices, availability, and review metadata in App Store Connect and Google Play Console
- Analyze subscription metrics, conversion funnels, and experiment results
- Diagnose setup issues like empty Offerings or failed sandbox purchases
Choose your starting point
You use Claude Code, Cursor, Codex, or Gemini CLI. Install the plugin. It bundles the skills and the MCP server in a single step.
Your environment doesn't support plugins. Install the skills on their own, then set up the MCP server manually.
You want to script setup, or work outside an agent. Use the CLI. It works the same way whether a person or an agent runs it.
You only need to read your data. The MCP Server on its own covers charts, experiments, and project configuration.
Authentication
Plugins and the MCP server authenticate with OAuth, so your agent gets access based on your RevenueCat account permissions across all your projects. The MCP server also accepts a RevenueCat API v2 secret key for clients that don't support OAuth.
To disconnect the toolkit later, revoke its token from Account → Security. See OAuth for how these connections work.
Example prompts
Set up RevenueCat for my fitness app. I'm building for iOS and Android. I want monthly and annual subscriptions.
Integrate RevenueCat in this React Native app and configure the SDK with the correct public API key.
My offerings are empty on iOS sandbox. Diagnose the RevenueCat setup and tell me what to fix.
The AI Toolkit or Rico?
The difference is whose agent does the work.
The AI Toolkit is for your agent. You bring Claude, Cursor, or Codex, install the toolkit, and your agent gains the access and the playbooks to build your integration.
Rico is ours. You don't install it and you don't point it at your codebase. It's already in the RevenueCat dashboard and available in Slack, and it works on your subscription business rather than your source code: diagnosing revenue and retention changes, interpreting experiments, benchmarking you against industry data, and building Paywalls from a description.
Next steps
- Install a plugin to set up your coding assistant in one step
- Ask Rico about your business from the dashboard or Slack