Monetization MCP server: get started

Overview

The Monetization Model Context Protocol (MCP) Server connects AI assistants like Claude or Gemini to the Equativ Monetization platform. It enables AI tools to retrieve real-time data and perform actions within Monetization accounts, transforming assistants from text generators into specialized assistants.

Monetization MCP server capabilities

The Monetization MCP is a read-only view onto Equativ's Monetization platform. Its tools allow for the following operations:

  • Reporting on delivery and revenue
  • Diagnosing deal delivery
    • Checking configuration for one or more deals.
    • Finding blocking delivery rules for an advertiser category, RTB advertiser, country, DSP, partner, format, or placement.
    • Searching and inspecting the rules that block demand or set floor prices.
    • Showing what Monetization holds about an advertiser or domain and which rules apply to it.
  • Record lookup and search
    • Querying entity types, including deals, insertions, campaigns, sites, placements, creatives, delivery rules or domain lists; includes also sub-resources such as targeting criteria and timeframes.
    • Listing the valid filter names for each entity.
  • Reference data and name resolution
    • Turning names into IDs and back, including advertiser categories, countries, DSPs, partners, or formats.
    • Finding which table a plain-language term belongs to, for example, a term existing in more than one taxonomy.
  • Account context
    • Showing which API user and network the connection is using.
    • Listing networks the token has permission to access.

Prerequisites

You need the following to connect your client to Monetization MCP:

  • An active Monetization account
  • A compatible MCP client:
    • Claude Desktop (Pro/Team/Enterprise)
    • Claude Code
    • Antigravity CLI
    • Microsoft Copilot Studio
    • Another MCP client: If you are using an MCP client not listed above, Equativ must manually allowlist it before you can connect (see “MCP client allowlisting” in the next section).

Authentication

MCP client allowlisting

Any MCP client not listed in the “Prerequisites” requires allowlisting by Equativ. If you attempt to connect with an unapproved client using OAuth, the connection will fail during login with an Invalid redirect_uri error.
In this case, proceed as follows:

  1. Copy the full URL from your browser's address bar. It will look like this:
    https://login.eqtv.io/login?client_id=EMP-MCP&code_challenge=<CODE_CHALLENGE>&code_challenge_method=S256&redirect_uri=<REDIRECT_URI>&resource=https://emp.mcp.eqtv.io&response_type=code&state=<STATE>
  2. Alternatively, determine the callback URL:
    1. Check your client's documentation for the "OAuth callback URL" or "redirect URI".
    2. If using an in-house application, locate the callback URL configured in your own OAuth client settings.
  3. Send the extracted <REDIRECT_URI> (or the full error URL) to your Equativ representative so they can add the domain to the allowlist.

Server URL

Monetization MCP server URL:

https://emp.mcp.eqtv.io/

Make sure to include the trailing slash /, as the registered Auth0 audience is strictly bound to https://emp.mcp.eqtv.io/.

The flow is handled automatically when the AI client supports OAuth for MCP.

Bearer Token

Request an access token from Auth0 and add it to the client configuration as a header: Authorization: Bearer <your-token>.

Setup

Claude Desktop

  1. Go to Settings > Customize > Connectors.
  2. Click Add customer connector. If your organization prohibits custom connectors, ask your administrator for authorization of the Monetization MCP https://emp.mcp.eqtv.io/.
  3. Enter the name “Monetization MCP”
  4. Enter the server URL: https://emp.mcp.eqtv.io/.
  5. Advanced Settings: Leave empty/default (authentication is handled automatically via OAuth).
  6. Authenticate:
    1. Claude will trigger the OAuth flow via Auth0 (auth.equativ.com).
    2. Sign in using your standard Equativ Monetization credentials.
    3. Once redirected back, the connector will display as connected.

Claude Code

claude mcp add emp --transport http https://emp.mcp.eqtv.io/

Antigravity CLI

Update the settings.json as follows:

{
  "mcpServers": {
    "emp": {
      "httpUrl": "https://emp.mcp.eqtv.io/",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

Microsoft Copilot (Copilot Studio)

  1. Open your agent in Copilot Studio.
  2. Go to the Tools page and select Add a tool > New tool > Model Context Protocol.
  3. Enter the server URL: https://emp.mcp.eqtv.io/.
  4. In the wizard, configure authentication with your bearer token.
  5. Save the tool and add it to your agent.

Copilot Studio requires the Streamable HTTP transport, which matches the Monetization MCP server's transport type.

Troubleshooting

Issue Solution
401 Unauthorized Verify bearer token validity and formatting.
Connection failed Check URL accuracy and network permissions.
Tools not appearing Restart AI client after configuration changes.
endDate in the future error Metrics and report end dates mustn't be in the future. Use current time minus one hour.
Missing time component Metrics and report dates require full datetime format: YYYY-MM-DDThh:mm:ss
401 Unauthorized despite a valid token Confirm with Equativ that your LLM instance has been whitelisted. Authentication will fail even with a valid bearer token or OAuth flow if the client instance is not whitelisted. For more information, see “MCP client allowlisting”, earlier in this document.