RevenueCat

MCP Server

** - Manage your In-app-purchases in [RevenueCat](https://www.revenuecat.com) without leaving your AI coding environment.

/ 100

6 capabilities

Capabilities6 decomposed

mcp-based revenuecat api integration for in-app purchase management

Medium confidence

Exposes RevenueCat's REST API through the Model Context Protocol (MCP) standard, allowing AI coding assistants and LLM agents to invoke RevenueCat operations (create subscriptions, manage entitlements, query customer data) without leaving the IDE or chat interface. Uses MCP's tool-calling schema to translate natural language requests into authenticated RevenueCat API calls, with automatic request/response marshaling and error handling.

Solves for

Query subscription status and entitlements for a specific customer without switching to RevenueCat dashboardCreate or modify in-app purchase offerings programmatically while coding the client appDebug customer billing issues by fetching transaction history and subscription state directly in the IDEAutomate subscription lifecycle operations (grant entitlements, revoke access, handle refunds) as part of development workflows

Best for

Mobile app developers integrating RevenueCat SDKs who want frictionless access to purchase data during development

AI-assisted development teams using Claude, ChatGPT, or other MCP-compatible LLMs to scaffold billing logic

DevOps/backend engineers automating subscription management tasks via AI agents

Requires

RevenueCat account with active API key (obtainable from RevenueCat dashboard)

MCP-compatible AI assistant or agent framework (e.g., Claude with MCP support, Anthropic SDK 0.7+, or custom MCP client)

Network access to RevenueCat API endpoints (api.revenuecat.com)

Limitations

Requires RevenueCat account and API key — no local-only operation possible

MCP protocol overhead adds ~100-300ms per request compared to direct REST calls

Limited to RevenueCat's API surface — cannot perform operations not exposed by RevenueCat's REST endpoints

What makes it unique

Bridges RevenueCat's REST API into the MCP ecosystem, enabling AI assistants to manage subscriptions and entitlements natively without custom API wrappers or external tools. Uses MCP's standardized tool schema to abstract RevenueCat's endpoint complexity, allowing LLMs to reason about purchase operations in natural language.

vs alternatives

Unlike direct RevenueCat SDK integration (which requires native code), MCP integration works across any MCP-compatible AI tool and IDE, reducing context-switching and enabling AI-driven automation of billing workflows without leaving the development environment.

customer subscription state querying with real-time entitlement resolution

Medium confidence

Retrieves live customer subscription data from RevenueCat, including active subscriptions, entitlements, expiration dates, and renewal status. Implements caching at the MCP layer to reduce API calls for repeated queries on the same customer within a session, and resolves entitlements based on the customer's current subscription state and any manually-granted access.

Solves for

Check if a user has an active subscription and which features they're entitled toVerify subscription renewal status and upcoming renewal dates for a customerRetrieve the full entitlement list for a customer to validate feature access in codeAudit customer subscription history to understand churn or upgrade patterns

Best for

Backend developers building feature-gating logic who want to validate entitlements during development

QA engineers testing subscription flows and entitlement grants without manual RevenueCat dashboard navigation

Support engineers debugging customer billing issues with AI-assisted investigation

Requires

Valid RevenueCat API key with read permissions

Customer ID (RevenueCat user ID or app-specific customer identifier)

Network connectivity to RevenueCat API

Limitations

Queries return point-in-time snapshots — no real-time streaming of subscription changes

Entitlement resolution depends on RevenueCat's backend state; local caching may be stale if subscriptions change outside the MCP session

No filtering or aggregation at the MCP layer — must retrieve full customer objects and filter in the AI agent

What makes it unique

Exposes RevenueCat's customer entitlement resolution logic through MCP, allowing AI agents to reason about subscription state without understanding RevenueCat's internal entitlement calculation rules. Abstracts the complexity of subscription status (active, expired, grace period, etc.) into a simple entitlements list.

vs alternatives

Faster than manually querying RevenueCat's dashboard for each customer; more reliable than client-side entitlement caching because it always reflects server-side truth from RevenueCat's backend.

subscription creation and modification with validation

Medium confidence

Enables programmatic creation of new subscriptions and modification of existing ones (e.g., upgrading, downgrading, pausing) through MCP tool calls. Validates subscription parameters (product ID, entitlements, pricing) against the app's offering configuration before submitting to RevenueCat, and returns confirmation with the new subscription state and any entitlements granted.

Solves for

Create a new subscription for a customer during onboarding flow testingUpgrade or downgrade a customer's subscription tier without manual RevenueCat dashboard accessPause or resume a subscription for testing subscription lifecycle scenariosGrant temporary entitlements or override subscription state for testing feature access

Best for

Mobile app developers testing subscription flows and entitlement grants in development

QA engineers automating subscription state transitions for test scenarios

Support teams using AI agents to manually grant entitlements or fix subscription issues

Requires

RevenueCat API key with write permissions (create/update subscriptions)

Valid product ID and offering ID from the app's RevenueCat configuration

Customer ID (existing or new)

Limitations

Write operations require elevated API key permissions — read-only keys will fail

No transaction rollback — if a subscription modification fails mid-operation, manual cleanup may be required

Validation is client-side only; server-side validation errors are returned asynchronously

What makes it unique

Wraps RevenueCat's subscription mutation endpoints in MCP's tool schema, allowing AI agents to reason about subscription state transitions in natural language (e.g., 'upgrade user to premium') and automatically handle the underlying API complexity. Includes client-side validation to catch configuration errors before hitting RevenueCat's API.

vs alternatives

More flexible than RevenueCat's dashboard for bulk or programmatic subscription changes; safer than direct API calls because MCP layer validates parameters and provides structured error feedback to the AI agent.

transaction history and revenue analytics querying

Medium confidence

Retrieves transaction logs, revenue metrics, and subscription analytics from RevenueCat through MCP, enabling AI agents to analyze customer purchase history, churn patterns, and revenue trends. Supports filtering by date range, product, customer, or transaction status, and returns aggregated metrics (MRR, churn rate, ARPU) if RevenueCat's analytics endpoints are exposed.

Solves for

Retrieve all transactions for a customer to audit billing history and identify refunds or chargebacksQuery revenue metrics (MRR, churn) for a specific period to understand business performanceAnalyze subscription upgrade/downgrade patterns to identify upsell opportunitiesExport transaction data for a cohort of customers for analysis or reporting

Best for

Finance and analytics teams using AI agents to generate revenue reports and insights

Product managers analyzing subscription metrics to inform pricing strategy

Customer success teams investigating churn and identifying at-risk customers

Requires

RevenueCat API key with analytics read permissions

Valid date range (ISO 8601 format)

Optional: customer ID, product ID, or transaction status filter

Limitations

Analytics endpoints may have higher latency (1-5s) compared to customer queries

Aggregated metrics (MRR, churn) are typically updated daily, not real-time

Date range filtering may be limited by RevenueCat's data retention policy (typically 2-3 years)

What makes it unique

Exposes RevenueCat's analytics and transaction APIs through MCP, allowing AI agents to perform ad-hoc revenue analysis and generate insights without switching to RevenueCat's dashboard or building custom reporting tools. Supports natural language queries like 'show me churn for Q3' that the AI agent translates to structured API calls.

vs alternatives

More accessible than RevenueCat's dashboard for non-technical stakeholders; faster than exporting data to spreadsheets because the AI agent can query, filter, and summarize in real-time.

offering and product configuration introspection

Medium confidence

Queries RevenueCat's app configuration (offerings, products, entitlements, pricing tiers) through MCP, allowing AI agents to understand the subscription structure without manual dashboard navigation. Returns the full offering tree with product IDs, entitlements, pricing, and trial configurations, enabling the agent to validate subscription operations against the app's actual configuration.

Solves for

Retrieve the list of available offerings and products to understand the subscription structureLook up entitlements associated with a specific product to validate feature access logicCheck pricing and trial configuration for a product before creating a subscriptionVerify that a product ID or offering ID is valid before attempting a subscription operation

Best for

Developers integrating RevenueCat SDKs who need to reference the app's offering structure during coding

QA engineers validating that offerings are correctly configured in RevenueCat

AI agents performing validation before executing subscription mutations

Requires

RevenueCat API key with read permissions

App ID (RevenueCat app identifier)

Limitations

Configuration is cached at RevenueCat's CDN — changes may take 5-10 minutes to propagate

No real-time notifications of configuration changes — agent must re-query to detect updates

Entitlements are returned as IDs only; no description or feature mapping data

What makes it unique

Exposes RevenueCat's offering configuration as queryable data through MCP, allowing AI agents to build a mental model of the app's subscription structure and validate operations against it. Acts as a schema registry for subscription operations, enabling the agent to catch configuration errors before hitting the API.

vs alternatives

Eliminates manual dashboard navigation to understand offerings; enables AI agents to self-validate subscription operations, reducing failed API calls and improving reliability.

entitlement grant and revocation with audit logging

Medium confidence

Allows manual granting or revocation of entitlements for a customer outside the normal subscription lifecycle, useful for testing, support interventions, or promotional access. Logs all entitlement changes with timestamp, reason, and operator ID, enabling audit trails for compliance and support investigations. Changes are immediately reflected in the customer's entitlements list.

Solves for

Grant a customer temporary premium access for testing or promotional purposesRevoke access to a feature if a customer's subscription is disputed or refundedOverride entitlements for a customer to test feature-gating logic without modifying their subscriptionAudit all entitlement changes for a customer to investigate access issues

Best for

Support teams using AI agents to quickly grant promotional access or fix entitlement issues

QA engineers testing feature-gating logic with manual entitlement overrides

Compliance teams auditing entitlement changes for regulatory requirements

Requires

RevenueCat API key with entitlement write permissions

Customer ID

Entitlement ID to grant or revoke

Limitations

Entitlement grants are not tied to subscriptions — if the subscription is modified, manually-granted entitlements may conflict

No automatic expiration — manually-granted entitlements persist until explicitly revoked

Audit logs are stored in RevenueCat's backend; no local export or real-time streaming

What makes it unique

Exposes RevenueCat's manual entitlement grant/revoke API through MCP with built-in audit logging, allowing AI agents to perform support interventions (e.g., granting promotional access) while maintaining compliance trails. Abstracts the complexity of entitlement lifecycle management.

vs alternatives

Faster than manual RevenueCat dashboard access for support teams; safer than direct API calls because MCP layer enforces audit logging and validates entitlement IDs before submission.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with RevenueCat, ranked by overlap. Discovered automatically through the match graph.

MCP Server24

Chargebee

** - MCP Server that connects AI agents to [Chargebee platform](https://www.chargebee.com).

subscription-lifecycle-management-via-agent-toolscustomer-data-retrieval-and-context-injectioncoupon-and-discount-application-via-agent-toolsmulti-currency-and-localization-support

4 shared capabilities

MCP Server32

mcp-boilerplate

A remote Cloudflare MCP server boilerplate with user authentication and Stripe for paid tools.

subscription-based recurring payment model with automatic access controlstripe-integrated payment processing with three monetization models

2 shared capabilities

MCP Server26

PayMCP

** (Python & TypeScript) - Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)

user/client credential validation and token managementrate limiting and quota enforcement per user/tool

2 shared capabilities

MCP Server25

MCP Servers Rating and User Reviews

** - Website to rate MCP servers, write authentic user reviews, and [search engine for agent & mcp](http://www.deepnlp.org/search/agent)

agent monetization and revenue sharingtier-based rate limiting and quota management

2 shared capabilities

MCP Server24

@restormel/mcp

MCP tool definitions for Restormel — models, providers, cost, routing, entitlements, and docs.

entitlements and usage quota enforcement via mcp tools

1 shared capability

Product30

MightyGPT

Transform WhatsApp and iMessage with GPT-3 AI chatbot...

user authentication and subscription management with billing integration

1 shared capability

Best For

✓Mobile app developers integrating RevenueCat SDKs who want frictionless access to purchase data during development
✓AI-assisted development teams using Claude, ChatGPT, or other MCP-compatible LLMs to scaffold billing logic
✓DevOps/backend engineers automating subscription management tasks via AI agents
✓Backend developers building feature-gating logic who want to validate entitlements during development
✓QA engineers testing subscription flows and entitlement grants without manual RevenueCat dashboard navigation
✓Support engineers debugging customer billing issues with AI-assisted investigation
✓Mobile app developers testing subscription flows and entitlement grants in development
✓QA engineers automating subscription state transitions for test scenarios

Known Limitations

⚠Requires RevenueCat account and API key — no local-only operation possible
⚠MCP protocol overhead adds ~100-300ms per request compared to direct REST calls
⚠Limited to RevenueCat's API surface — cannot perform operations not exposed by RevenueCat's REST endpoints
⚠No built-in caching or rate-limiting — relies on RevenueCat's rate limits (typically 100 req/s per API key)
⚠Requires MCP-compatible AI tool (Claude, etc.) — not usable with basic chat interfaces
⚠Queries return point-in-time snapshots — no real-time streaming of subscription changes

Requirements

RevenueCat account with active API key (obtainable from RevenueCat dashboard)MCP-compatible AI assistant or agent framework (e.g., Claude with MCP support, Anthropic SDK 0.7+, or custom MCP client)Network access to RevenueCat API endpoints (api.revenuecat.com)Understanding of RevenueCat's data model (apps, offerings, entitlements, customers)Valid RevenueCat API key with read permissionsCustomer ID (RevenueCat user ID or app-specific customer identifier)Network connectivity to RevenueCat APIRevenueCat API key with write permissions (create/update subscriptions)

Input / Output

Accepts: natural language queries (e.g., 'get subscription status for user 12345'), structured parameters (customer ID, app ID, offering ID), JSON payloads for complex operations (subscription modifications, entitlement grants), customer ID (string), optional filters (app ID, entitlement ID), customer ID, product ID, offering ID, optional: entitlements array, custom attributes, date range (start_date, end_date), optional filters: customer_id, product_id, transaction_status, optional: aggregation level (daily, monthly), app ID, optional: offering ID or product ID filter, entitlement ID, operation type (grant or revoke), optional: expiration date, reason/note

Produces: structured JSON responses (customer objects, subscription details, entitlement lists), transaction history (timestamps, amounts, status), error messages with RevenueCat error codes, customer object with subscriptions array, entitlements array with expiration timestamps, subscription metadata (product ID, purchase date, renewal date), subscription object with new state, entitlements array reflecting the new subscription, confirmation timestamp and transaction ID, transaction array with timestamp, amount, status, customer ID, aggregated metrics object (MRR, churn_rate, ARPU, transaction_count), time-series data for charting (daily/monthly revenue, churn), offerings array with product IDs, entitlements, pricing, products array with trial configuration, pricing tiers, entitlements array with IDs and metadata, confirmation with updated entitlements list, audit log entry with timestamp and operator ID, error message if entitlement ID is invalid

UnfragileRank

Adoption15%(25% weight)

Quality22%(25% weight)

Ecosystem15%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit RevenueCat→

About

** - Manage your In-app-purchases in [RevenueCat](https://www.revenuecat.com) without leaving your AI coding environment.

Alternatives to RevenueCat

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of RevenueCat?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities6 decomposed

mcp-based revenuecat api integration for in-app purchase management

Medium confidence

Solves for

Best for

Mobile app developers integrating RevenueCat SDKs who want frictionless access to purchase data during development

AI-assisted development teams using Claude, ChatGPT, or other MCP-compatible LLMs to scaffold billing logic

DevOps/backend engineers automating subscription management tasks via AI agents

Requires

RevenueCat account with active API key (obtainable from RevenueCat dashboard)

MCP-compatible AI assistant or agent framework (e.g., Claude with MCP support, Anthropic SDK 0.7+, or custom MCP client)

Network access to RevenueCat API endpoints (api.revenuecat.com)

Limitations

Requires RevenueCat account and API key — no local-only operation possible

MCP protocol overhead adds ~100-300ms per request compared to direct REST calls

Limited to RevenueCat's API surface — cannot perform operations not exposed by RevenueCat's REST endpoints

What makes it unique

vs alternatives

customer subscription state querying with real-time entitlement resolution

Medium confidence

Solves for

Best for

Backend developers building feature-gating logic who want to validate entitlements during development

QA engineers testing subscription flows and entitlement grants without manual RevenueCat dashboard navigation

Support engineers debugging customer billing issues with AI-assisted investigation

Requires

Valid RevenueCat API key with read permissions

Customer ID (RevenueCat user ID or app-specific customer identifier)

Network connectivity to RevenueCat API

Limitations

Queries return point-in-time snapshots — no real-time streaming of subscription changes

Entitlement resolution depends on RevenueCat's backend state; local caching may be stale if subscriptions change outside the MCP session

No filtering or aggregation at the MCP layer — must retrieve full customer objects and filter in the AI agent

What makes it unique

vs alternatives

Faster than manually querying RevenueCat's dashboard for each customer; more reliable than client-side entitlement caching because it always reflects server-side truth from RevenueCat's backend.

subscription creation and modification with validation

Medium confidence

Solves for

Best for

Mobile app developers testing subscription flows and entitlement grants in development

QA engineers automating subscription state transitions for test scenarios

Support teams using AI agents to manually grant entitlements or fix subscription issues

Requires

RevenueCat API key with write permissions (create/update subscriptions)

Valid product ID and offering ID from the app's RevenueCat configuration

Customer ID (existing or new)

Limitations

Write operations require elevated API key permissions — read-only keys will fail

No transaction rollback — if a subscription modification fails mid-operation, manual cleanup may be required

Validation is client-side only; server-side validation errors are returned asynchronously

What makes it unique

vs alternatives

transaction history and revenue analytics querying

Medium confidence

Solves for

Best for

Finance and analytics teams using AI agents to generate revenue reports and insights

Product managers analyzing subscription metrics to inform pricing strategy

Customer success teams investigating churn and identifying at-risk customers

Requires

RevenueCat API key with analytics read permissions

Valid date range (ISO 8601 format)

Optional: customer ID, product ID, or transaction status filter

Limitations

Analytics endpoints may have higher latency (1-5s) compared to customer queries

Aggregated metrics (MRR, churn) are typically updated daily, not real-time

Date range filtering may be limited by RevenueCat's data retention policy (typically 2-3 years)

What makes it unique

vs alternatives

More accessible than RevenueCat's dashboard for non-technical stakeholders; faster than exporting data to spreadsheets because the AI agent can query, filter, and summarize in real-time.

offering and product configuration introspection

Medium confidence

Solves for

Best for

Developers integrating RevenueCat SDKs who need to reference the app's offering structure during coding

QA engineers validating that offerings are correctly configured in RevenueCat

AI agents performing validation before executing subscription mutations

Requires

RevenueCat API key with read permissions

App ID (RevenueCat app identifier)

Limitations

Configuration is cached at RevenueCat's CDN — changes may take 5-10 minutes to propagate

No real-time notifications of configuration changes — agent must re-query to detect updates

Entitlements are returned as IDs only; no description or feature mapping data

What makes it unique

vs alternatives

Eliminates manual dashboard navigation to understand offerings; enables AI agents to self-validate subscription operations, reducing failed API calls and improving reliability.

entitlement grant and revocation with audit logging

Medium confidence

Solves for

Best for

Support teams using AI agents to quickly grant promotional access or fix entitlement issues

QA engineers testing feature-gating logic with manual entitlement overrides

Compliance teams auditing entitlement changes for regulatory requirements

Requires

RevenueCat API key with entitlement write permissions

Customer ID

Entitlement ID to grant or revoke

Limitations

Entitlement grants are not tied to subscriptions — if the subscription is modified, manually-granted entitlements may conflict

No automatic expiration — manually-granted entitlements persist until explicitly revoked

Audit logs are stored in RevenueCat's backend; no local export or real-time streaming

What makes it unique

vs alternatives

Faster than manual RevenueCat dashboard access for support teams; safer than direct API calls because MCP layer enforces audit logging and validates entitlement IDs before submission.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to RevenueCat

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

RevenueCat

Capabilities6 decomposed

mcp-based revenuecat api integration for in-app purchase management

customer subscription state querying with real-time entitlement resolution

subscription creation and modification with validation

transaction history and revenue analytics querying

offering and product configuration introspection

entitlement grant and revocation with audit logging

Related Artifactssharing capabilities

Chargebee

mcp-boilerplate

PayMCP

MCP Servers Rating and User Reviews

@restormel/mcp

MightyGPT

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to RevenueCat

Are you the builder of RevenueCat?

Get the weekly brief

Data Sources

RevenueCat

Capabilities6 decomposed

mcp-based revenuecat api integration for in-app purchase management

customer subscription state querying with real-time entitlement resolution

subscription creation and modification with validation

transaction history and revenue analytics querying

offering and product configuration introspection

entitlement grant and revocation with audit logging

Related Artifactssharing capabilities

Chargebee

mcp-boilerplate

PayMCP

MCP Servers Rating and User Reviews

@restormel/mcp

MightyGPT

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to RevenueCat

Are you the builder of RevenueCat?

Get the weekly brief

Data Sources