Skip to main content
Performance demand only. AdsMCP surfaces are headless: there is no client context to verify an impression against, so impression-priced demand (Direct and Programmatic CPM) does not serve. CPA demand and filtered CPC demand serve fully. See Choosing your integration path for why.
AdsMCP is a remote-hosted MCP server that connects MCP-capable apps and agents to the Agentic Ad Server in minutes. It is the right path when your surface is an agent runtime, an MCP tool platform, or any environment where nothing renders in a browser. More at adsmcp.ai.

​
Endpoint

Transport: MCP Streamable HTTP. Registry listing: io.github.Adgentek/adsmcp in the official MCP Registry.

​
Tool names

The hosted server currently registers five tools: Some client interfaces display dots as underscores, such as ads_serve. Use the names returned by your client’s tool list. See the complete tool reference for inputs and response behavior. There is no ads.report or ads.track tool.

​
Client setup

​
Claude Desktop

Remote connectors are configured through Claude’s connector settings, including when you use Claude Desktop:
  1. Open Customize → Connectors.
  2. Select Add → Custom → Web.
  3. Enter a name and https://mcp.adgentek.ai/mcp.
  4. Choose No sign in.
  5. Add a request header named Authorization with the value Bearer YOUR_PUBLISHER_TOKEN.
  6. Add the connector.
Team-plan connectors may require an Owner or Primary Owner. See Anthropic’s remote connector guide for current account-specific controls.

​
Generic Streamable HTTP client

The endpoint requires a publisher key. Authorization: Bearer … is the recommended authentication scheme and works for generic Streamable HTTP clients and fixed request headers in Claude.

​
Billing and tracking on AdsMCP

There is no impression pixel on a headless surface. Two events matter: Delivery confirmation and billing notice (burl). When a filled tool response explicitly includes auction_id, call confirm_ad_delivery once after presentation. The get_video_ad_vast tool supplies this ID on fill. Do not infer an auction ID when another response does not supply one. The server records the confirmation and performs demand-side billing reconciliation. You never receive or call the burl directly. Repeating a confirmation is safe but unnecessary because the operation is idempotent. Clicks. Always use the click URL from the ad payload. Clicks route through the Adgentek redirect layer where click-quality filtering runs; this is what makes CPC demand billable from an agent surface. Never pass the advertiser’s destination URL directly to the user. Do not attempt to fire impression URLs from your infrastructure. Server-fired impressions are classified as invalid traffic and discarded, and repeated server-side impression firing will fail integration review. The demand you can serve (CPA, filtered CPC) is priced so that no impression verification is needed.