AI Connectors

Connect ChatGPT, Claude, Gemini, and custom runtimes to Attribution.ai through the MCP JSON-RPC transport.

Use OAuth + PKCE when your client supports it. Use API keys for automation or clients that do not complete OAuth flows.

MCP Endpoint

https://attribution.ai/api/mcp/rpc

Send JSON-RPC requests with tools/list and tools/call methods to execute workspace-scoped measurement tools.

Recommended Auth: OAuth + PKCE

Use OAuth by default for interactive connector setup.

Discovery metadata:

• /.well-known/oauth-authorization-server
• /.well-known/oauth-protected-resource

OAuth endpoints:

• POST /api/mcp/authorize
• POST /api/mcp/token
• POST /api/mcp/register

ChatGPT

1. Open connector or MCP settings in ChatGPT.
2. Add server URL https://attribution.ai/api/mcp/rpc.
3. Use OAuth when prompted (recommended), or Bearer API key if required.
4. Start a new conversation and run a discovery query.

Claude

1. Open Claude connector settings (desktop, web, or Claude Code).
2. Configure server URL https://attribution.ai/api/mcp/rpc.
3. Complete OAuth or provide API key header configuration.
4. Verify by asking for revenue by channel for a specific date range.

Gemini

1. Open MCP/connector settings in Gemini or Google AI tooling.
2. Add https://attribution.ai/api/mcp/rpc.
3. Authenticate with OAuth + PKCE.
4. Confirm tools are discovered before running deeper analysis prompts.

Custom Agent Runtimes

For internal copilots, autonomous analysts, or CI jobs, use the same endpoint and auth model as interactive connectors. For terminal-first pipelines, pair this with the CLI.

API Key Fallback

If a client cannot complete OAuth, use a bearer API key generated from Connect Your AI.

curl -s -X POST https://attribution.ai/api/mcp/rpc \
 -H "Content-Type: application/json" \
 -H "Authorization: Bearer atai_your_key_here" \
 -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

Validation Checklist

• Connector can complete OAuth authorization code flow with PKCE (or uses a valid key).
• initialize, tools/list, and tools/call succeed.
• 401 responses include WWW-Authenticate resource metadata.
• Queries return workspace-scoped data and respect per-minute rate limits.