Developers / MCP

Connect your agent to Riptide

Use MCP to let your agent configure inventory, manage campaigns, and query reports in Riptide. Tools share schemas with the admin API and respect your tenant permissions. Registered agents use signed requests and configurable limits on the actions they can take.

Riptide Console model registry with baseline and shadow bid models
AI agents · Models

Example tools

ToolWhen to use it
riptide.supply.create_placementDefine an ad slot before integrating it into a site or app. Set its floor price and media settings.
riptide.supply.create_ip_listStart an IP list for line-item targeting. Import and publish its ranges before using it to include or exclude traffic.
riptide.supply.verify_supply_documentReview supply identity and authorization records. Check an ads.txt or sellers.json document and save the result for inspection.
riptide.campaign.create_line_itemTurn a campaign order into delivery instructions by booking a line item under it.
riptide.demand.create_dealRecord a negotiated buying arrangement as a preferred, guaranteed, or private deal.
riptide.demand.set_marketplace_dealsGroup negotiated deals into a marketplace so placements can use the selected demand together.
riptide.demand.create_routeConnect an external buyer so it can receive eligible bid requests through a demand route.
riptide.reporting.run_reportInvestigate delivery or revenue by querying a report with the metrics, dimensions, and date range you need.
riptide.model.assign_modelEvaluate a model before expanding its use. Assign it to shadow evaluation, a limited A/B test, or live traffic.
riptide.operability.explain_requestInvestigate why an ad request produced a particular result by inspecting its decision trace stage by stage.
riptide.sales.create_media_buyBook eligible inventory products through AdCP Sales by creating a media buy.

Connect to POST /mcp using protocol version 2025-06-18, initialize a session, then discover the tools your credentials permit. The MCP guide covers sessions, request signing, and approval tasks. REST tool discovery and invocation are also available.

Control what your agent can do

Each call runs as an authenticated user or agent in one tenant. For registered agents, signed requests establish the agent's identity. Set limits on spending and actions, require human approval where needed, and pause activity when usage spikes. Changes leave audit records for review.

Protocol interoperability

The gateway also supports AdCP sales, signals, and creative tools, along with Trusted Match, UCP context, and A2A transaction integrations. Check the standards guide for the scope of each integration, including IAB AAMP and ARTF alignment and external protocol conformance.

Start with an MCP client

Use the integration toolkit to inspect the tools your credentials can access, then adapt its client for your agent.

Put this into practice

Download the examples · All feature guides