FullVision

Setup

Connect a cloud AI agent to the FullVision MCP Server

The FullVision MCP Server lets a cloud AI agent (Claude, Cursor, or any MCP-compatible client) query your analytics in plain language — no SDK, no SQL, no exports. The agent discovers what's available and answers questions directly against your live data.

Use it when you would rather ask "which channel drove the most revenue last month?" than write the query that answers it.

It exposes 32 tools — reports, entities, audiences and experiments — covering revenue (Stripe), web traffic, attribution, conversion funnels, SEO (Google Search Console), product engagement, audience segmentation and experimentation. See Tools for the full tool list.

1. Browser connectors (claude.ai, ChatGPT)

Both connect through the browser — no API key to copy or paste. Claude Code, Codex, Cursor and VS Code use the key-based setup in section 2.

claude.ai

Settings → Connectors → Add custom connector, URL https://data.fullvision.io/mcp. You're redirected to sign in and approve a workspace in the browser.

ChatGPT

Requires developer mode (Plus, Pro, Business, Enterprise or Education; web only). On Business and Enterprise, a workspace admin enables it first in Workspace Settings → Permissions & Roles → Connected Data. Same URL: https://data.fullvision.io/mcp.

Only workspace owners can authorize a connector, and the connection is read-only.

A connector appears in Settings → API keys as a named key. Revoking that key disconnects it.

2. Key-based clients (Claude Code, Cursor, VS Code, Codex)

Mint a key with read access

Open MCP in the dashboard and mint a key — it is shown once, and the same page renders the config below with the key already filled in. The key encodes your workspace, so it only ever returns your data.

The server admits a key only if it carries read scope (read:*, or any of revenue:read, web:read, search:read, attribution:read, customer:read). The events key on the Setup page is events:write and is refused with 403.

Add the server to your MCP client

Add this to Claude Desktop, Claude Code, Cursor, or any MCP-compatible client:

{
  "mcpServers": {
    "fullvision": {
      "url": "https://data.fullvision.io/mcp",
      "headers": {
        "Authorization": "Bearer sk_your_key"
      }
    }
  }
}

Replace sk_your_key with your FullVision API key.

CLI clients take it in one command instead:

# Claude Code
claude mcp add --transport http fullvision https://data.fullvision.io/mcp \
  --header "Authorization: Bearer sk_your_key"

# Codex — reads the token from an env var
export FULLVISION_API_KEY="sk_your_key"
codex mcp add fullvision --url https://data.fullvision.io/mcp \
  --bearer-token-env-var FULLVISION_API_KEY

3. Verify

Ask your agent: "Which channel drove the most new-customer revenue last month?" It should call channel-report and answer from the rows. If it does, you're connected.

How to use it

You don't call tools by hand — you ask business questions, and the agent picks the report and parameters. A typical turn:

  1. The agent calls check_data_health when the answer will drive a spend or pricing decision.
  2. It calls the report that matches the question — channel-report, page-report, keyword-report, ad-report, email-report, form-report — with from / to and, on a group form, limit and granularity.
  3. It reads the returned rows and answers in plain language.

Just ask naturally. Examples that work out of the box:

  • "Which channel drives the most new-customer revenue over the last 90 days?"
  • "Top landing pages by revenue this month, marketing site only."
  • "Which Google Search queries convert to revenue?"
  • "Which paid campaigns have the worst LTV-to-CAC ratio?"
  • "Build me an audience of people who hit pricing twice in 30 days and never paid, and sync it to Google Ads."
  • "Set up an A/B test on my pricing hero and tell me when it has a verdict."

There is no raw SQL and no schema browsing on this surface. If a question isn't answerable from a report, say so — the fix is a new report, not a query.

Endpoint

https://data.fullvision.io/mcp

Transport: Streamable HTTP · Auth: Authorization: Bearer sk_…

On this page