MCP

Get started

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

Endpoint

Streamable HTTP (stateless JSON responses) at:

https://mcp.openrevenue.com/mcp

https://mcp.openrevenue.com/mcp

Authentication

Pass an account API key (same keys as the REST API), or complete OAuth 2.1:

Authorization: Bearer openrevenue_your_api_key_here

Authorization: Bearer openrevenue_your_api_key_here

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

OpenRevenue ships as a ChatGPT / Codex plugin backed by this MCP server. Prefer the Plugins Directory listing when available. For development:

1. In ChatGPT, open Settings → Apps & Connectors → Advanced and enable developer mode.
2. Create a connector and paste the MCP URL:

https://mcp.openrevenue.com/mcp

https://mcp.openrevenue.com/mcp

Complete OAuth when prompted (sign in on OpenRevenue and approve scopes). ChatGPT does not use API keys for this connector. Example prompts: “How did example.com do this week?”, “Top referrers for example.com last 30 days”, “Funnel conversion for signup on example.com”.

Cursor

Add a remote MCP server in Cursor settings (MCP), or merge into your MCP config:

{  "mcpServers": {    "openrevenue": {      "url": "https://mcp.openrevenue.com/mcp",      "headers": {        "Authorization": "Bearer openrevenue_your_api_key_here"      }    }  }}

{  "mcpServers": {    "openrevenue": {      "url": "https://mcp.openrevenue.com/mcp",      "headers": {        "Authorization": "Bearer openrevenue_your_api_key_here"      }    }  }}

Claude Desktop

Remote MCP with custom headers (Claude Desktop / Claude Code, when remote MCP is enabled):

{  "mcpServers": {    "openrevenue": {      "url": "https://mcp.openrevenue.com/mcp",      "headers": {        "Authorization": "Bearer openrevenue_your_api_key_here"      }    }  }}

{  "mcpServers": {    "openrevenue": {      "url": "https://mcp.openrevenue.com/mcp",      "headers": {        "Authorization": "Bearer openrevenue_your_api_key_here"      }    }  }}

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.

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.

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; write calls are capped more tightly.