# Choose the product — AdBuyMCP

One platform with explicit buying boundaries for AdBuyMCP, DOOHMCP and CTVMCP.

## Product boundaries

| Product | Permitted buying channels | Deployment target |
| --- | --- | --- |
| AdBuyMCP | Search, social, CTV, audio, addressable TV, cinema and DOOH. | Parent production hostname must be configured. |
| DOOHMCP | DOOH only. | doohmcp.com is the intended specialist domain. |
| CTVMCP | CTV only. Addressable TV is a separate channel. | ctvmcp.com is the intended specialist domain. |

## Separate connections, shared organization

Each hosted product has its own MCP resource URL and matching API deployment. Signed tokens bind the product and permitted channels; a request parameter cannot select a broader product.

The API and MCP both enforce scope. A mixed-media campaign belongs on AdBuyMCP. Specialist requests cannot use a persisted ID to operate on excluded sibling channels.

All products use the advertiser organization and shared wallet. Documentation downloads describe a product; downloading another product's schema does not grant its permissions.

## Verify the service before connecting

A configured domain or example URL is not proof that a service is deployed. Check the published platform metadata, OAuth discovery and exact product contracts, then complete a real authenticated acceptance flow.

These documentation pages remain readable without a workspace session. Campaign data and execution remain authenticated.