Skip to content
MCP

SSO Authentication

Connect Teads MCP clients with SSO, including Gemini Enterprise's custom data store setup.

Use SSO when a person is at the keyboard. Most MCP clients handle the OAuth 2.0 Authorization Code Flow with PKCE. Point the client at the Teads MCP URL, then sign in in the browser. For these clients, you do not request a token yourself or put secrets in the client config. Gemini Enterprise uses a custom MCP data store with separate OAuth settings. Follow its tab below.

What to expect with standard clients

  1. Add Teads MCP to your client. This guide covers Cursor, Claude, ChatGPT, Codex, MCP Inspector, and Microsoft Copilot Studio.
  2. Complete Teads sign-in when the client asks you to authenticate.
  3. The client stores the token and sends it with MCP requests.
  4. Tools such as list_my_seats appear when Teads MCP is enabled for your organisation.

MCP URL:

https://public-api.teads.tv/mcp/v1/agency

Choose a client below. Standard SSO clients only need the MCP URL. Gemini Enterprise has separate Google Cloud and OAuth settings in its tab.

Add a remote server in MCP settings, or create .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "teads-agency": {
      "url": "https://public-api.teads.tv/mcp/v1/agency"
    }
  }
}

After saving:

  1. Enable the teads-agency server.
  2. Complete Teads sign-in when the client opens the browser.
  3. Confirm tools such as list_my_seats and campaign_read appear in the MCP tools list.

Do not put a personal SSO token into a shared agent or CI job. Use M2M instead.

Getting started with Teads MCP

Connect AI assistants to Teads campaign and reporting tools over Model Context Protocol.

M2M Authentication

Obtain a Teads MCP access token with OAuth2 client credentials on the public API token route.

On this page

What to expect with standard clients