Authentication

The Adthena MCP server uses OAuth 2.0 to authenticate users. You sign in with your existing Adthena credentials — no API keys to manage.

How It Works

You ──sign in──> Adthena (Auth0) ──token──> MCP Server ──authorized──> Adthena API

You connect to the MCP server from your MCP client (e.g., Claude.ai, Claude Desktop, or any other MCP-compatible client)
The client redirects you to the Adthena login page (powered by Auth0)
You sign in with your Adthena email and password (or SSO if configured)
Auth0 issues a token which the MCP server verifies
The server maps your authenticated email to your authorized Adthena accounts
Each tool call is checked against your account permissions before execution

You never handle API keys directly. The server resolves the correct API key for each account internally.

After authentication, you can only access accounts that are linked to your Adthena user:

Your first tool call should be list_accessible_accounts to see which accounts you have access to
Each subsequent tool call requires an account_id — the server verifies you're authorized for that account
If you need access to additional accounts, ask your Adthena admin

Property	Value
Protocol	OAuth 2.0 Authorization Code Flow
Identity Provider	Auth0 (OIDC)
Token Verification	ID token (JWT)
Scopes	`openid`, `profile`, `email`, `offline_access`

The following callback URLs are registered for common MCP clients:

Client	Callback URL
Claude.ai	`https://claude.ai/api/mcp/auth_callback`
Claude.ai (alternate)	`https://claude.com/api/mcp/auth_callback`
Claude Desktop	`http://localhost:6274/oauth/callback`
Claude Desktop (debug)	`http://localhost:6274/oauth/callback/debug`

The server accepts requests from: