MCP

Hosted Model Context Protocol server for agents that need to read and act on your analytics.

Get started

1Create an API key from Account → API. Prefer read-only unless the agent must change data.
2Add the MCP URL and Bearer token to your client (or use OAuth)
3Ask the agent about a project by domain (e.g. example.com)

Endpoint

Streamable HTTP (stateless JSON responses) at:

text

https://api.reignat.com/mcp

https://api.reignat.com/mcp

Authentication

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

http

Authorization: Bearer reignat_your_api_key_here

Authorization: Bearer reignat_your_api_key_here

ℹ

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.

Cursor

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

json

{  "mcpServers": {    "reignat": {      "url": "https://api.reignat.com/mcp",      "headers": {        "Authorization": "Bearer reignat_your_api_key_here"      }    }  }}

{  "mcpServers": {    "reignat": {      "url": "https://api.reignat.com/mcp",      "headers": {        "Authorization": "Bearer reignat_your_api_key_here"      }    }  }}

Claude Desktop

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

json

{  "mcpServers": {    "reignat": {      "url": "https://api.reignat.com/mcp",      "headers": {        "Authorization": "Bearer reignat_your_api_key_here"      }    }  }}

{  "mcpServers": {    "reignat": {      "url": "https://api.reignat.com/mcp",      "headers": {        "Authorization": "Bearer reignat_your_api_key_here"      }    }  }}

OAuth

MCP clients that support OAuth discover the authorization server from protected-resource metadata at https://api.reignat.com/.well-known/oauth-protected-resource. Access tokens are JWTs verified against https://www.reignat.com/api/auth/jwks. Users always approve access on Reignat'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 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.