Skip to main content
Listed in the official MCP Registry as com.openrevenue/mcp. Also powers the OpenRevenue ChatGPT plugin.

Get started

1
For ChatGPT, Claude and Cursor, connect with OAuth (below). For clients that only support API keys, create a key from Account → API. Prefer read-only unless the agent must change data.
2
Add the MCP URL (and Bearer token for API-key clients), or complete OAuth
3
Ask about a project by domain (e.g. example.com)

Endpoint

Streamable HTTP (stateless JSON responses) at:

Authentication

Pass an account API key (same keys as the REST API), or complete OAuth 2.1:
Session cookies are never accepted on MCP. Keep keys server-side and rotate them from Account → API if exposed. Unauthenticated requests return WWW-Authenticate with protected-resource metadata for OAuth discovery.

Scopes

  • read — list projects and analytics (default for new read-only keys).
  • write — create/update projects and funnels; create/delete goals and funnels (implies read).
Keys created before scopes shipped keep full read write access until rotated.

ChatGPT

Install the OpenRevenue ChatGPT plugin from the Plugins Directory, then connect your account with OAuth. Ask things like “How did example.com do this week?”, “Top referrers for example.com last 30 days”, or “Funnel conversion for signup on example.com”. For development or custom connectors, enable Settings → Apps & Connectors → Advanced developer mode in ChatGPT and paste this MCP URL:
Complete OAuth when prompted. ChatGPT does not use API keys for this connector.
The ChatGPT listing uses this same Universal MCP URL with OAuth. Create an API key only for other MCP clients that do not support OAuth.

Cursor

Add OpenRevenue as an MCP server in Cursor. Cursor signs you in with OAuth, so no API key is needed.
1
Open ~/.cursor/mcp.json to use OpenRevenue in every project, or .cursor/mcp.json inside one project. Create the file if it does not exist.
2
Add the server:
3
Open Customize in the Cursor sidebar, enable openrevenue, then sign in to OpenRevenue and approve access when Cursor prompts you.
4
Ask a question, for example “Top referrers for example.com last 30 days”.
To use an API key instead of OAuth, add an Authorization header:

Claude

Add OpenRevenue as a custom connector. It works in Claude on the web, Claude Desktop and Cowork, and you sign in with OAuth, so no API key is needed.
1
In Claude, open Customize → Connectors, click Add, then Add custom connector.
2
Enter OpenRevenue as the name and paste the MCP URL:
3
Keep the detected sign-in settings, finish adding the connector, then sign in to OpenRevenue and approve access.
4
Ask a question, for example “How did example.com do this week?”
Claude starts with read access. The first time you ask it to change something, such as creating a goal, it asks you to approve write access.

Claude Code

Add the server from your terminal, then run /mcp in Claude Code to sign in:
To use an API key instead of OAuth:

OAuth

MCP clients that support OAuth discover the authorization server from protected-resource metadata at https://mcp.openrevenue.com/.well-known/oauth-protected-resource/mcp. Access tokens are JWTs verified against https://www.openrevenue.com/api/auth/jwks. Users always approve access on OpenRevenue’s consent screen. Prefer API keys for personal agents; use OAuth when the client cannot store a long-lived key.
  • OAuth scope mcp (or read) grants read tools only.
  • Request write in addition when the agent must create or change data.
  • A read-only token that calls a write tool gets a 403 with WWW-Authenticate: Bearer error="insufficient_scope", so clients that support scope step-up can ask the user for write access and retry.

Disconnect an app

Apps you connect with OAuth stay connected until you disconnect them. To see and remove them:
  1. Open Account → API.
  2. Under Connected apps, find the app. Each entry shows its name and domain, what it can do and when you connected it.
  3. Click Revoke and confirm.
The app loses access right away: its next MCP request gets a 401 with WWW-Authenticate: Bearer error="invalid_token". To use it again, connect it from the app and approve access on the consent screen. API keys are not affected; delete them under API keys on the same page.

Tools

Read tools cover account profile, projects, stats, timeseries, pages, referrers, geo, devices, browsers, OS, visitors, performance, funnels, and goals. Write tools (owner/admin + write scope) can create/update projects and funnels, and create goals. Deleting a funnel or goal requires confirm: true after the user approves.

Periods

Tools that take a period accept only the values below and reject anything else. The default is 30d. Not available via MCP (use the dashboard): deleting projects, team invites, billing, or connecting revenue / Search Console credentials.

Permissions

  • Read tools need the read scope plus project access (owner or member).
  • Write tools need the write scope plus owner or team admin.
  • Every tool call is written to a durable audit log (user, tool, outcome).
  • Rate limits apply separately from the REST API and per user for both API keys and OAuth; write calls are capped more tightly.