Claude reads the same numbers you do.
Connect Claude or Cursor with your MIRA FIVE sign-in, and ask about buyers, channels and goals in plain words.
Sample conversation in Claude, connected to MIRA FIVE. Question: “Where did last month's buyers come from?” Answer, Buyers by channel: Organic search 24, Direct 22, Paid search 21.
Claude, Cursor and other agents read your MIRA FIVE numbers through its Model Context Protocol (MCP) server at https://app.mirafive.io/mcp. They sign in over OAuth, read by default, and change setup only after you allow it.
Read by default, set up when allowed.
Forty-one tools: some read what your dashboard shows, the rest set up, run tests and switch flags once you allow it.
What an agent reads
- Overview and key numbers
- People, one person, and segments
- Journeys and funnels
- Channels, campaigns and landing pages
- Google Search Console and Google Ads
- Goals, events, insights and dashboards
- Experiments, feature flags and their results
What it sets up, once allowed
- Projects and sources
- Actions and goals
- Funnels and segments
- Insights and dashboards
- Feature flags and experiments
You decide what an agent may change.
Read-only is the default, and setup waits for a switch you turn on per connection.
- Sign-in
- OAuth with your own MIRA FIVE account, or an API key
- Default
- Read-only
- Setup
- After you switch on “May change setup” for that connection
- Live changes
- Turning a flag on or off, changing a flag that is on, or starting or ending an experiment also needs “May turn flags on and off”
- Deleting
- Agents never delete
- Audit
- Every call is recorded, every change audited
Connected in three steps.
Works with Claude Code, Claude Desktop, claude.ai, Cursor, VS Code, ChatGPT and other MCP clients.
Copy the address
One address for every client and every account.
One address for every client and every account.
Add it to your client
In Claude, add it as a custom connector. In Cursor or VS Code, add it as an MCP server.
Sign in and approve
A browser window opens MIRA FIVE. Sign in and approve the connection.
Questions worth asking first.
Where did last month's buyers come from?
Which campaigns gained or lost buyers against the month before?
What did our latest customer do before buying?
Where do people drop out between cart and payment?
What does each Google Ads campaign cost per buyer?
Plan an A/B test on the checkout button, decided by paid orders.
Questions about agents.
Can an agent change or delete anything?
Which clients can connect?
Does the agent see the same numbers as my team?
Is there a REST API as well?
Let Claude answer from your numbers.
Create a free project and add the address to Claude. Then ask where your buyers came from.