revenuecat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVENUECAT_API_KEY | Yes | Your RevenueCat secret API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_subscriberB | Get subscriber info, entitlements, and subscription status for a user. |
| check_entitlementA | Check if a user has an active entitlement (e.g. "premium", "pro"). |
| get_offeringsA | Fetch available subscription offerings and packages for a user. |
| grant_entitlementB | Grant a promotional entitlement to a user for a specified duration. |
| revoke_entitlementA | Revoke a promotional entitlement from a user. |
| delete_subscriberB | Delete a subscriber and all their purchase history. Use with caution. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: fetching subscriber info, checking a specific entitlement, retrieving offerings, granting/revoking entitlements, and deleting subscribers. The purposes are clearly separated with no meaningful overlap.
All tool names follow the consistent verb_noun snake_case pattern (e.g., get_subscriber, grant_entitlement, revoke_entitlement). This makes the API predictable and easy to navigate.
Six tools is a well-scoped number for a subscription management server. Each tool serves a clear purpose without redundancy or unnecessary bloat.
The server covers the core read and write operations for subscriber and entitlement management. Minor gaps exist such as lack of subscriber attribute updates or bulk listing, but the essential lifecycle is well represented.