Connect your agent
Sign in, choose a buyer account, and verify your connection before making changes.
Connect through the gateway
Use Streamable HTTP and the gateway URL below:
https://ai-gateway.magnite.com/mcp/server/orchestration- Choose a client. Open Orchestration client setup and copy the instructions for your client.
- Sign in and choose an account. Select the ClearLine buyer account you intend to use. Product discovery and buy operations use this account context.
- Discover capabilities. Call
get_adcp_capabilitiesto check the supported AdCP version, buying modes, and account model. - Verify a read. Call
get_productswithbuying_mode: "wholesale"andpagination: { "max_results": 5 }. Confirm that it succeeds in the selected account before creating a buy.
A connection indicator or tools/list alone does not verify account access. An empty product result can be valid; an authentication or tool error is not a successful check.
Sign-in and account selection · Missing picker or failed call
Connect to demo products
Ask your Magnite contact for the demo gateway URL and add it as a separate
MCP connection. Sign in and select your authorized ClearLine buyer account as
usual. Call get_products to verify the demo catalog before creating a buy.
The demo connection limits product discovery and product selection for new buys or packages to the designated demo publisher account's products. Your account still needs access to that publisher account; an empty catalog does not grant additional access. Optional agent tools are not available on this connection. Magnite-owned Streaming and DV+ products are excluded; use the publisher-owned Direct IO demo products.
This is not a dry run: it uses your real ClearLine account. Existing campaign and creative operations are not isolated from production. Use only the agreed demo campaigns and creatives, and confirm the demo supply setup with your Magnite contact before purchasing. Do not add a query parameter to your normal gateway URL to switch modes; use the separate URL provided to you.
Call from your own code
Supply a valid user bearer token and the exact authorized account context. ClearLine buyers use clearline/dsp_sub/ACCOUNT_ID. The account ID must belong to your authenticated identity.
See Call from code for the SDK pattern and the difference between aggregate and direct tool names.
The client-facing gateway uses Streamable HTTP. The downstream Orchestration endpoint uses JSON-RPC over HTTP/SSE and currently advertises MCP protocol version 2024-11-05. Let your MCP SDK negotiate with the gateway instead of configuring the client's transport from the downstream implementation.

