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

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

​
Tool names

Tool names registered with dots are sanitized to underscores by MCP clients. The name you call is the sanitized one:
Registered conceptName your client sees
ads.serveads_serve
Verify the live tool list by connecting and listing tools; treat the endpoint, not this page, as authoritative for names.

​
Client setup

​
Claude Desktop

Add the server as a custom connector: Settings, Connectors, Add custom connector, then enter the endpoint URL and your publisher token when prompted.

​
Generic Streamable HTTP client

{
  "mcpServers": {
    "adsmcp": {
      "url": "https://mcp.adgentek.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PUBLISHER_TOKEN"
      }
    }
  }
}

​
Billing and tracking on AdsMCP

There is no impression pixel on a headless surface. Two events matter: Billing notice (burl). Fired server-side on impression receipt. This is the only legitimate server-side tracking event in the Adgentek stack. Fire it exactly once per received ad, immediately on receipt. 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.