MCP Server
Connect AI tools like Claude Code and Cursor to your attribution data via the Model Context Protocol
Atribu provides a hosted Model Context Protocol (MCP) server that gives AI tools direct access to your attribution data. Ask questions in natural language and get answers grounded in real campaign performance, customer journeys, and revenue data.
What you can do
- "What's my ROAS this month?" -- get headline KPIs with spend, revenue, and attribution coverage
- "Which campaigns should I kill?" -- detect creative fatigue and identify underperformers
- "Show me the journey for this customer" -- trace every touchpoint from first click to payment
- "Compare last week to the week before" -- period-over-period analysis with delta percentages
- "Are there any anomalies?" -- automatic z-score anomaly detection across spend, revenue, and traffic
- "Send these conversions to Meta" -- push attributed conversions to Meta CAPI for optimization
How it works
Atribu's MCP server is centrally hosted at https://mcp.atribu.app/mcp. Your AI tool connects over OAuth -- there is no local installation, no server setup and, for the clients on Connect an AI client, no token to copy either. A personal access token stays available for scripts and CI.
The server exposes 52 tools that return structured, semantically-labeled data. All reasoning and narration happens on the AI tool's side -- Atribu provides the data, your AI provides the analysis.
Quickstart
Connect in under 2 minutes
Connect an AI client
The exact config for Claude, Claude Code, Cursor, ChatGPT and the rest
Connect to Claude
One-click OAuth connector for Claude Desktop & Claude.ai
Authentication
Token scopes, rate limits, and metering
Available Tools
All 52 tools with parameters and examples
Write-Back (Meta CAPI)
Push conversions to Meta with safety rails
Supported AI tools
The MCP server works with any tool that supports the Streamable HTTP transport:
| Tool | Transport | Status |
|---|---|---|
| Claude Code (CLI) | Streamable HTTP | Supported |
| Claude Desktop | Streamable HTTP | Supported |
| Cursor | Streamable HTTP | Supported |
| Windsurf | Streamable HTTP | Supported |
| VS Code (Copilot) | Streamable HTTP | Supported |
| ChatGPT (developer mode) | Streamable HTTP | Supported |
| Any MCP-compatible client | Streamable HTTP | Supported |
The exact configuration for each one is on Connect an AI client.
Key design decisions
No AI on the server. The MCP server returns structured data with semantic labels, units, and metadata. Your AI tool interprets the data and generates the narrative. This means zero LLM inference cost on Atribu's side and you always get the latest model capabilities from your AI tool.
Explicit scope per call. Every tool call specifies which workspace and profile to query. There's no "active workspace" state on the server, so concurrent AI sessions using the same token are safe.
PII masked by default. Customer emails, phone numbers, and names are masked unless you explicitly request unmasking with the right token scope and workspace setting.
Weighted metering. Tools cost different amounts of units depending on complexity. Listing workspaces is free; sending conversions to Meta costs 10 units. Your plan includes a monthly unit allowance.