Getting Started

The Comscore MCP uses OAuth 2.0 authorization code flow backed by Comscore SSO. No separate account or password is needed — your existing Comscore credentials handle everything.

1. 1
   Your AI client initiates the OAuth flow and redirects to the Comscore authorization endpoint.
2. 2
   You authenticate with your existing Comscore credentials — the same ones used to access Comscore products.
3. 3
   On approval, the client receives an access token valid for 1 hour, plus a refresh token valid for 4 hours.
4. 4
   All subsequent MCP calls carry the access token as a Bearer credential in the Authorization header.
5. 5
   When the access token expires, the client refreshes it silently using the refresh token — until the refresh token expires after 4 hours, at which point you sign in again.

The server is RFC 9728-compliant. A standard OAuth 2.0 client can discover all authorization endpoints automatically from:

Each user must be provisioned for MCP access before they can authenticate. Comscore provisions access on request, typically within 1–2 business days. This is a one-time step per user.

• OAuth 2.0 authorization code flow (PKCE recommended)
• Bearer token in the Authorization header
• Token refresh on 401 response

The server follows the published MCP specification and does not require any Comscore-specific client modifications. Any MCP-compatible client that implements these OAuth requirements should work.

Protocol: Model Context Protocol (MCP), HTTP transport with Server-Sent Events (SSE).

The server is compatible with any client that implements the MCP specification. Currently confirmed working: Claude Code, Claude Desktop, and ChatGPT (paid/Developer Mode).