Connect the RevenueCat API

• ✓ Products & entitlements
• ✓ Offerings & packages
• ✓ Customers & subscriptions
• — Write operations
• — Webhooks (Poll via the customer/subscription tools)

accounts_

get · project identity

apps_

list · get

products_

list · get

entitlements_

list · get

offerings_

list · packages

customers_

get · subscriptions · purchases

OAuth scopes requested

• Read your project identity
• Read apps and products
• Read entitlements and offerings
• Read customers, subscriptions and purchases

# Add Modiva's MCP server to your agent
{
  "mcpServers": {
    "modiva": {
      "url": "https://mcp.modiva.ai",
      "headers": { "Authorization": "Bearer $MODIVA_MCP_KEY" }
    }
  }
}

# Then connect RevenueCat and call its tools, e.g.
accounts_list(provider="revenuecat")

How do I connect the RevenueCat API with Modiva?

Create a Modiva account, generate an MCP key, and connect RevenueCat from your dashboard. Modiva runs the full OAuth flow and stores the encrypted token for you — no client secrets in your code.

What can I do with the RevenueCat API through Modiva?

Read subscriptions, products, entitlements, offerings, packages and customers across your RevenueCat project. You get 12 typed tools grouped by resource (accounts_, apps_, products_, entitlements_, offerings_, customers_), callable over REST or the MCP server.

Do I need to handle OAuth or token refresh myself?

No. Modiva handles the RevenueCat OAuth handshake, token storage (envelope-encrypted) and automatic refresh. You call a single unified endpoint.

Can an AI agent use the RevenueCat API?

Yes — that is the point. Modiva exposes RevenueCat as Model Context Protocol (MCP) tools, so agents like Claude, Cursor or your own app can read and act on RevenueCat through one endpoint.