Connect to Claude
Add Atribu as a native connector in Claude Desktop or Claude.ai with one-click OAuth — no token to copy or paste
If you use Claude Desktop or Claude.ai (web), the easiest way to connect is as a custom connector. You paste the Atribu MCP URL once, sign in, and approve — Claude handles authentication over OAuth. There's no atb_user_ token to generate, copy, or store.
Two ways to connect
- Claude Desktop / Claude.ai → add Atribu as a custom connector (this page). One-click OAuth, no token.
- Claude Code, Cursor, scripts, CI → use a personal access token instead. See the Quickstart.
Add the connector
Open Settings → Connectors.
Click Add custom connector.
Paste the Atribu MCP URL and confirm:
https://mcp.atribu.app/mcpA sign-in window opens. Log in to Atribu (the same account you use at atribu.app).
Review the access being requested, choose your scopes, and click Allow. Claude is now connected.
Open Settings → Connectors.
Click Add custom connector.
Paste the Atribu MCP URL:
https://mcp.atribu.app/mcpLog in to Atribu in the window that opens, then click Allow on the consent screen.
Plan requirement
Custom connectors on Claude.ai are available on Claude's paid plans. Exact menu labels may differ slightly between Claude versions.
The consent screen
Before connecting, Atribu shows you exactly what Claude is asking for: the account you're signed in as, the scopes requested, and that the connection covers all workspaces you belong to.
Grant only the scopes you actually need:
| Scope | What it allows | Recommended |
|---|---|---|
Read analytics (mcp:read) | Attribution, campaigns, creatives, journeys — personal data masked | ✅ For most users |
Read unmasked PII (mcp:read_pii) | Unmask email/phone/name when you explicitly ask | Only if you need it |
Write-back (mcp:write) | Send conversions to Meta CAPI (send_meta_conversions) | Only if you need it |
Leave PII and write-back unchecked unless you need them
If Claude requests all scopes, you can uncheck the ones you don't want before clicking Allow — Read analytics alone is enough to ask about performance. Read-PII still requires your workspace to be in full-PII mode, and Write-back still requires a workspace admin to enable it, so checking them never bypasses your workspace's own controls.
Try it out
Open a chat in Claude and ask about your ad performance:
What's my ROAS this month? Which campaigns are performing best?Claude calls the right Atribu tools and answers from your real data. If you belong to multiple workspaces, it will ask which one to use.
Manage connected apps
Every connection is listed in Developer → Connected Apps in the Atribu dashboard. There you can see which apps you've authorized, the scopes they hold, and when they were last used.
To revoke access, click Disconnect — the app loses access immediately. It can reconnect later by authorizing again.
Connector vs. token revocation
Disconnecting a connector here revokes the OAuth grant (and the short-lived tokens it issued). Personal access tokens are managed separately under Developer → MCP Tokens.
When to use a token instead
The custom connector is best for interactive use in Claude Desktop and Claude.ai. For everything else, create a personal access token:
- Claude Code and Cursor — configured with a header-based token
- Scripts, automations, CI — anywhere there's no interactive sign-in
Troubleshooting
- The sign-in window doesn't appear, or Claude says it can't connect. Double-check the URL is exactly
https://mcp.atribu.app/mcp(with the/mcppath). Confirm the server is reachable:curl https://mcp.atribu.app/health/liveshould return{ "status": "ok" }. - "Add custom connector" isn't available on Claude.ai. Custom connectors require a paid Claude plan. Claude Desktop also supports them.
- Claude keeps asking which workspace. That's expected if you belong to more than one — name the workspace in your prompt, or ask Claude to "list my workspaces" first.
- You want to start over. Disconnect under Developer → Connected Apps, then add the connector again.