August 24, 20262 min read

Introducing Reignat MCP

Egger & Co
Egger & Co
Company

You can now connect Cursor, Claude, and other MCP clients straight to Reignat — with the same API key you already use for the REST API.

What is MCP?

Model Context Protocol (MCP) is how AI tools talk to external products in a structured way. Instead of copy-pasting dashboards into chat, the agent calls tools — list projects, pull stats, build a funnel — and gets real data back.

What you can do

With the hosted Reignat MCP server, agents can:

  • List the projects your API key can access
  • Read stats, timeseries, pages, referrers, geo, devices, browsers, and OS
  • Inspect visitors, funnels, goals, and Core Web Vitals
  • Create or update projects (name, timezone)
  • Create, update, or delete funnels and goals — when you have manage access

How to connect

1. Create an account API key from Account → API.

2. Add this remote MCP server in Cursor or Claude:

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

Full setup details live in the MCP docs.

Permissions and safety

Read tools work for any project you can access. Write tools require owner or team admin — the same checks as the dashboard. High-risk actions stay out of MCP for now: deleting projects, billing, team invites, and connecting revenue or Search Console secrets.

Why we built it

Teams already ask agents to summarize traffic and propose funnels. A hosted MCP endpoint means one URL to allowlist, one key model you already trust, and workflows that can both analyze and act — without browser CSRF or brittle screenshots.

Ready to try it? Generate an API key and point your agent at https://api.reignat.com/mcp.

Share