Vercel Analytics in Claude, Cursor and your own code

Why an API when Vercel has one?

Vercel’s Web Analytics API returns one project at a time and needs a Vercel token with access to the whole team. Lookout already reads it for you and keeps the results together: boards, previous-period comparisons, goals, campaigns, alerts. The Lookout API exposes that layer, so a script or an AI assistant gets “every landing page on the Acme board, with the change against last week” in one call, using a key that only sees your workspace and, unless you allow it, can only read.

Three ways in

• MCP server. Connect Claude, Cursor or Claude Code and ask questions in plain language. The assistant calls Lookout tools such as get_board or compare_sites and answers with your real data. The server is open source (MIT): lookout-mcp on GitHub.
• REST API. JSON for the same numbers the dashboard shows, for Google Sheets, Notion, n8n or your own backend.
• Webhooks. Lookout sends a signed POST when an alert fires, a site spikes or drops, a digest or report goes out, a new project without Web Analytics appears, or a project turns Analytics on. Slack and Discord incoming-webhook URLs work as they are.

Keys

1. Open Settings → API & MCP and create a key. Give it a name that says what will use it, for example “Notion dashboard”. Only workspace owners can create keys; members can’t.
2. Copy it once. Lookout shows the full key one time and keeps only a hash. If you lose it, revoke it and create another.
3. Use it as a bearer token. A key is read-only unless you tick Allow notes and exports when you create it. Every key is scoped to its workspace and limited to 600 requests an hour. Over the limit you get a 429 with a Retry-After header.

Revoking a key takes effect on the next request, including for MCP clients configured with it. The list shows when each key was last used, so unused keys are easy to spot.

Setting up MCP

The server speaks Streamable HTTP at mcp.lookoutstats.com and uses your API key as a bearer token. Paste the configuration for your client, replace the key, and restart it.

{
  "mcpServers": {
    "lookout": {
      "url": "https://mcp.lookoutstats.com",
      "headers": {
        "Authorization": "Bearer lk_live_your_key_here"
      }
    }
  }
}

Claude Desktop: Settings → Developer → Edit config. On claude.ai: Settings → Connectors → Add custom connector, with the same URL and key.

Once connected, the assistant has these tools:

Read tools never change anything. The two write tools, add_annotation and export_board, need a key created with Allow notes and exports. They do what the buttons in the app do: a note shows on the board’s charts like any other, and an export is the same file the Export button makes. Try asking: “Which landing page dropped most this week, and what deployed right before?” or “Compare the three pricing pages over the last 30 days, indexed.”

The REST API

Reads are GET and work with any key; adding a note and making an export link are POST and need a key with Allow notes and exports. Reads take the same range values as the app (24h, 7d, 30d, or a custom range of up to 30 days written 2026-10-01..2026-10-14) and return the previous period alongside, so a change percentage never has to be computed on your side.

curl "https://api.lookoutstats.com/v1/boards/3f6c2a9e-8b1d-4c7a-9e2f-5d4b8a1c7e60/sites?range=7d" \
  -H "Authorization: Bearer lk_live_your_key_here"

Responses come from the same cache as the dashboard, refreshed about every 15 minutes, so polling faster doesn’t give newer numbers. The OpenAPI description is at /v1/openapi.json.

Webhooks

1. Add an endpoint in Settings → API & MCP: an HTTPS URL and the events you want.
2. Verify the signature. Each request carries X-Lookout-Signature, an HMAC-SHA256 of the body with the endpoint’s secret, in hex. The secret is shown in the endpoint’s settings, with a Copy button.
3. Send a test. A ping event arrives immediately so you can check the receiving side before anything real happens.

Events: alert.fired, site.spike, site.drop, digest.sent, report.sent, project.discovered, analytics.enabled. A failed delivery is retried three times with increasing delay; the last 30 days of deliveries, with status and timing, are listed under Recent deliveries, and a failed one can be sent again with one click. Pausing an endpoint keeps it and its history but stops sending.

{
  "id": "6b1e0c4a-2f7d-4e93-a8c5-1d9f3b7e2a40",
  "event": "site.drop",
  "created_at": "2026-10-16T09:00:00.000Z",
  "workspace_id": "org_2nT8kQ4xWvLm",
  "data": {
    "site": { "id": "prj_launch", "domain": "launch.northwind.io" },
    "range": "7d",
    "visitors": 1840,
    "previous_visitors": 2674,
    "change": -31.2,
    "url": "https://lookoutstats.com/projects/prj_launch"
  }
}

If the URL is a Slack or Discord incoming webhook, Lookout formats the event as a readable message instead of sending the raw JSON.

What a key can’t do

Nothing that changes how your workspace is set up: no editing boards, members, alerts or settings, no reading other workspaces, and no access to your Vercel token. A key with Allow notes and exports can add chart notes and make export links, nothing more. Keys are tied to the workspace, not to the person who created them, so they keep working when a teammate leaves; revoke a key to stop it. When the workspace disconnects a Vercel team, that team’s sites drop out of every answer. Creating and revoking keys, changes to webhook endpoints and notes added through MCP are written to the workspace’s security log.

Who this is for

Agencies that already report in Sheets or Notion, developers who want deploy-and-traffic questions answered in their editor, and anyone who would rather be told about a drop than go looking for it. If you just want to see the boards, you don’t need any of this; the live demo shows the dashboard itself, and share links cover the “show a client” case without a key.