Documents https://mcp.revenuecat.ai/mcp, subscription configuration, charts, and experiments. This is documentation evidence, not a connection or tool-execution test. Separate endpoint observation on October 5, 2026 at 02:45:30 UTC: one anonymous discovery request to https://mcp.revenuecat.ai/mcp returned HTTP 401 (authentication required). Authentication is expected under the publisher’s setup instructions. The check stopped at authentication; tool and resource capabilities were not inspected, and protocol compliance and security remain unassessed.
Documents OAuth where supported and API v2 secret-key authentication. Permissions depend on the account or key.
Unauthenticated public HTTP GET; no MCP tools invoked. A reachable source does not establish tool behavior, security, or compatibility with your client.
Before you install: EveryMCP has not security-audited this listing or independently verified its publisher. Review the linked repository, requested permissions, deployment model, and official-registry record where applicable. How the catalog works →
Follow RevenueCat's publisher setup documentation. Connect to https://mcp.revenuecat.ai/mcp using OAuth where supported or a RevenueCat API v2 secret key with appropriate account/key permissions.
Treat this as catalog metadata, not an audited command. Confirm current instructions in the linked sources before running it.
Use Cases
• Project and app configuration
• Product and Offering management
• Charts and experiment analysis
Tags
subscriptionsmobilerevenuecatiap
Choose a starting stack
The free planner offers three-server shortlists for five common goals. It does not automatically include RevenueCat MCP or confirm compatibility with your environment.
Rolling out your first MCP workflow? The $49 starter kit provides a selection matrix, permission record, client example, and acceptance/rollback checklist. It does not certify RevenueCat MCP or provide managed setup.