RevenueCat MCP integration for AI agents.
Connect AI agents to RevenueCat through 12 structured actions, including get customer, get overview metrics, and get revenue metric. Review authentication, i…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the RevenueCat integration exposes
The RevenueCat Agent App exposes 12 provider-backed actions for finance, developer tools, and subscriptions work. Its current contract lets an authorized agent retrieve a revenuecat customer and optionally expand the customer's attributes, retrieve overview metrics for a revenuecat project, and retrieve total revenuecat project revenue for an inclusive date range. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected RevenueCat account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real RevenueCat capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve a RevenueCat customer and optionally expand the customer's attributes.
INPUTS: projectId / customerId / expand
get_overview_metricsREADRetrieve overview metrics for a RevenueCat project.
INPUTS: projectId / currency
get_revenue_metricREADRetrieve total RevenueCat project revenue for an inclusive date range.
INPUTS: projectId / startDate / endDate / currency / revenueType
get_subscriptionREADRetrieve a RevenueCat subscription by its subscription ID.
INPUTS: projectId / subscriptionId
list_customer_active_entitlementsREADList the entitlements currently active for a RevenueCat customer.
INPUTS: projectId / customerId / startingAfter / limit
list_customer_subscriptionsREADList subscriptions belonging to a RevenueCat customer.
INPUTS: projectId / customerId / startingAfter / limit
list_customersREADList customers in a RevenueCat project, optionally searching by email or customer identifier.
INPUTS: projectId / startingAfter / limit / search
list_entitlementsREADList entitlement definitions configured in a RevenueCat project.
INPUTS: projectId / startingAfter / limit
list_offeringsREADList offerings configured in a RevenueCat project, optionally expanding packages and products.
INPUTS: projectId / startingAfter / limit / expand
list_productsREADList products configured in a RevenueCat project.
INPUTS: projectId / startingAfter / limit
list_projectsREADList RevenueCat projects accessible to the configured secret API key.
INPUTS: startingAfter / limit
search_subscriptionsREADFind subscriptions by a store subscription identifier such as an Apple transaction ID or Google order ID.
INPUTS: projectId / storeSubscriptionIdentifier / includeScheduled
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
projectIdREQUIRED- RevenueCat project ID.
customerIdREQUIRED- RevenueCat customer or app user ID.
expandOPTIONAL- Optional customer fields to expand in the response.
get_overview_metrics
projectIdREQUIRED- RevenueCat project ID.
currencyOPTIONAL- Currency used for the returned RevenueCat metrics.
get_revenue_metric
projectIdREQUIRED- RevenueCat project ID.
startDateREQUIRED- Inclusive start date in ISO 8601 format.
endDateREQUIRED- Inclusive end date in ISO 8601 format.
currencyOPTIONAL- Currency used for the returned RevenueCat metrics.
revenueTypeOPTIONAL- Revenue definition returned as the metric value.
get_subscription
projectIdREQUIRED- RevenueCat project ID.
subscriptionIdREQUIRED- RevenueCat subscription ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve a RevenueCat customer and optionally expand the customer's attributes. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerVerify with Get Overview Metrics
Retrieve overview metrics for a RevenueCat project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_overview_metricsSAFETY BOUNDARY
Operate RevenueCat with explicit limits
- Authorize RevenueCat with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned RevenueCat data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `customer_information:customers:read`, `charts_metrics:overview:read`, `customer_information:subscriptions:read`, and `project_configuration:entitlements:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the RevenueCat task completed successfully.
CONNECTION MODEL
API key
RevenueCat REST API v2 secret API key sent as a Bearer token. Create a V2 secret key in the RevenueCat project settings API keys page: https://www.revenuecat.com/docs/welcome/authentication.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by RevenueCat.