RevenueCat MCP Server Setup
Configure RevenueCat MCP Server for cloud or local deployment
Authentication Overview
RevenueCat MCP Server offers two authentication methods depending on your client:
- OAuth Authentication: Available for VSCode and Cursor - provides seamless authentication without managing API keys
- API v2 Secret Key: Supported by all MCP clients - requires a RevenueCat API v2 secret key
Choose the method that works best for your client setup.
Cloud MCP Server Setup
Using with Claude Code
Add the server via the claude
CLI command:
claude mcp add --transport http revenuecat https://mcp.revenuecat.ai/mcp --header "Authorization: Bearer YOUR_API_V2_SECRET_KEY"
Using with Cursor
You can add the MCP server to Cursor by clicking the button below:
Or you can also add it manually by adding the following to your mcp.json
file:
{
"servers": {
"revenuecat": {
"url": "https://mcp.revenuecat.ai/mcp",
"headers": {
"Authorization": "Bearer {your API v2 token}"
}
}
}
}
Using with VS Code Copilot
Add to your Visual Studio Code mcp.json
:
{
"servers": {
"revenuecat-mcp": {
"url": "https://mcp.revenuecat.ai/mcp",
"type": "http"
}
},
"inputs": []
}
Using with Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"revenuecat": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.revenuecat.ai/mcp",
"--header",
"Authorization: Bearer ${AUTH_TOKEN}"
],
"env": {
"AUTH_TOKEN": "YOUR_API_V2_SECRET_KEY"
}
}
}
}
Using with MCP Inspector
For testing and development:
npx @modelcontextprotocol/inspector@latest
Configure the inspector with:
- Transport Type: Streamable HTTP
- URL:
https://mcp.revenuecat.ai/mcp
- Authentication: Bearer Token with your RevenueCat API v2 secret key
Authentication Methods
RevenueCat Cloud MCP Server supports two authentication methods:
OAuth Authentication (Recommended)
OAuth provides a seamless authentication experience without needing to manage API keys manually. Currently supported clients:
- Visual Studio Code - Automatic OAuth flow for seamless authentication
- Cursor - Automatic OAuth flow for seamless authentication
We'll extend this list as more clients add OAuth support.
API v2 Secret Key Authentication
All MCP clients support API v2 secret key authentication. This method requires manually providing your RevenueCat API v2 secret key in the client configuration.
Getting Your API Key
- Open your RevenueCat dashboard
- Navigate to your project's API Keys page
- Create a new API v2 secret key and copy it
💡 Tip: Create a dedicated API key for the MCP server to keep your credentials organized.
⚠️ Permissions:
- Use a write-enabled key if you plan to create/modify resources
- A read-only key works if you only need to view data
🔧 Third-Party Integration:
If you'd like to integrate your services with RevenueCat MCP Server, please contact us at RevenueCat Support so we can set up OAuth clients for your application.
Local MCP Extension Setup
1. Install Extension
- Open VS Code or Cursor
- Go to Extensions marketplace
- Search for "RevenueCat MCP"
⚠️ Visual Studio Marketplace:
This only works if your VS Code fork has access to the Visual Studio Marketplace.
If not, you can install the extension manually by downloading the VSIX file.
- Click Install
2. Configure Extension
- Open Command Palette (
Cmd+Shift+P
orCtrl+Shift+P
) - Run: RevenueCat: Set Project Secret Key
- Paste your API key when prompted
This creates an mcp.json
file in your workspace with the MCP server configuration.
🔒 Security: Add
mcp.json
to your.gitignore
to avoid committing your API credentials.
3. Enable MCP in Cursor
- Go to Cursor Settings → MCP
- Click the Enable button
- Click the Refresh icon to activate the server
VS Code Extension Commands
The local extension provides additional VS Code commands for key management:
Command | Description |
---|---|
RevenueCat: Set Project Secret Key | Set or update your API key |
RevenueCat: Remove Project Secret Key | Delete your stored API key |
RevenueCat: Show your project secret key | Display your current API key (masked) |