Skip to main content

​
Overview

Claude is one of the fastest ways to work with Provalytics data without leaving your normal workflow. Once connected, Claude can help your team inspect performance, summarize findings, pressure-test recommendations, and answer questions from live Provalytics data instead of static exports.

​
What you need

Before starting, make sure you have:
  • access to the MCP Server Access page in Provalytics
  • the correct client workspace selected
  • a user-specific API key
  • Claude access that supports custom MCP connections

​
Step 1: Generate your Provalytics API key

In Provalytics:
  1. Open MCP Server Access
  2. Confirm the correct client workspace is selected
  3. Enter a key name such as Claude Desktop or Claude Code
  4. Click Generate key
The key is scoped to that client’s data only. MCP Server Access overview

​
Step 2: Connect in Claude Desktop

For Claude Desktop, use the custom connector path shown on the MCP access page. In Claude Desktop:
  1. Go to Settings
  2. Open Integrations
  3. Choose Add custom connector
  4. Paste the Provalytics MCP URL shown in your workspace
The URL format shown in Provalytics is: https://mcp.getprova.com/mcp?token=YOUR_KEY Replace YOUR_KEY with the API key generated for your user. Leave OAuth fields blank unless your Claude environment specifically requires something different.

​
Step 3: Connect in Claude Code

For command-line workflows, Claude Code can connect to the same client-scoped MCP server. Use the command shown on the MCP access page: 
claude mcp add prova --transport http https://mcp.getprova.com/mcp?token=YOUR_KEY
Replace YOUR_KEY with your own user-specific key.

​
Step 4: Test the connection

After setup, ask a few basic questions to confirm the connection is working, such as:
  • what are my top channels by incrementality this month?
  • what does the optimizer recommend next?
  • how well did the latest model fit actual results?
If Claude answers from live Provalytics data, the connection is working.

​
Security notes

  • each user should create their own key
  • keys are read-only
  • keys are client-scoped
  • keys should be revoked when no longer needed
If a key is no longer in use, revoke it from the MCP Server Access page.

​
What Claude can help with

Claude is especially useful for:
  • turning dashboard findings into client-ready summaries
  • checking campaign performance without exporting files
  • reviewing recommendations before meetings
  • comparing modeled outcomes, efficiency, and forecast signals quickly