RevenueCat MCP Server Setup
Configure RevenueCat MCP Server for your AI assistant
Authentication Overview
RevenueCat MCP Server offers two authentication methods depending on your client:
- OAuth Authentication: Available for VS Code, Cursor, and Claude - 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 Web and Desktop
Use Anthropic’s custom connectors with a remote MCP server. Full product steps and security notes are in Get started with custom connectors using remote MCP.
Remote MCP server URL: https://mcp.revenuecat.ai/mcp
Pro and Max (individual)
- Open Settings → Connectors.
- In the Connectors section, choose Add custom connector.
- Enter the URL above.
- Choose Add, then Connect and finish authentication when prompted.
Team and Enterprise
- An Owner (or Primary Owner) adds the connector under Organization settings → Connectors → Add custom connector using the URL above.
- Each member opens Settings → Connectors, finds the custom connector (labeled Custom), and chooses Connect to authenticate.
Custom remote MCP connectors are in beta on Claude; free plans can use one custom connector.
Using with OpenAI Codex
The Codex app, CLI, and IDE Extension share MCP settings. If you’ve already configured MCP servers in one, they’re automatically adopted by the others.
You can add the MCP server via the Codex app:
- Open Settings → MCP Servers → Add custom server.
- Give it a name, choose Streamable HTTP, enter the url
https://mcp.revenuecat.ai/mcpand click Save.
Or you can add the MCP manually directly to your Codex configuration file (~/.codex/config.toml):
macOS/Linux:
[mcp_servers.revenuecat]
command = "npx"
args = ["mcp-remote", "https://mcp.revenuecat.ai/mcp", "--header", "Authorization: Bearer ${AUTH_TOKEN}"]
env = { AUTH_TOKEN = "YOUR_API_V2_SECRET_KEY" }
type = "stdio"
startup_timeout_ms = 20_000
Windows:
[mcp_servers.revenuecat]
command = 'C:\Program Files\nodejs\npx.cmd'
args = ["mcp-remote", "https://mcp.revenuecat.ai/mcp", "--header", "Authorization: Bearer ${AUTH_TOKEN}"]
env = {
APPDATA = 'C:\Users\USERNAME\AppData\Roaming',
LOCALAPPDATA = 'C:\Users\USERNAME\AppData\Local',
HOME = 'C:\Users\USERNAME',
SystemRoot = 'C:\Windows',
AUTH_TOKEN = "YOUR_API_V2_SECRET_KEY"
}
type = "stdio"
startup_timeout_ms = 20_000
On Windows, replace USERNAME with your actual Windows username.
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 — OAuth flow in MCP configuration
- Cursor — OAuth flow in MCP configuration
- Claude Web and Desktop — Add
https://mcp.revenuecat.ai/mcpas a remote MCP custom connector. - OpenAI Codex — Add
https://mcp.revenuecat.ai/mcpas a custom MCP server.
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
Create a dedicated API key for the MCP server to keep your credentials organized.
- Use a write-enabled key if you plan to create/modify resources
- A read-only key works if you only need to view data
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.