Connecting

Your buyer agent connects to the Orchestration Agent as a remote MCP server.

Connection URL

Connect through the MCP gateway using the Orchestration Agent's server alias, orchestration:

The gateway passes requests through to the Orchestration Agent, which speaks MCP over Server-Sent Events using JSON-RPC 2.0 (protocol version 2024-11-05) and identifies itself as adcp-mcp ("Orchestration Agent").

Authentication

Buyer agents authenticate on every request. Supported methods:

• Embed token — a Magnite-issued JWT in the x-api-key header. This is the typical path for external agents.
• Auth0 bearer token — Authorization: Bearer <token>.
• Session — for browser-based clients already signed in to Magnite.

Select the buyer account a request acts on with the x-auth-context header. The Orchestration Agent shares the same authentication pipeline as Magnite's other MCP servers. Credentials are issued by your Magnite contact.

Client setup

Your agent connects the same way as any Magnite MCP client. Rather than duplicate the mechanics here, see:

• Getting Started — add the server and authorize.
• Client setup — copy setup values for your tool.

First call

After connecting, call adcp_get_adcp_capabilities first to learn which AdCP versions, protocols, and buying modes this seller supports. See Capabilities.

To list the available tools directly:

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }