Full Ad Server for AI Applications

Ad revenue for AI apps.
One tool call.

AdsMCP is a full ad server hosted as a remote MCP. Serve live programmatic demand, bring your own direct-sold campaigns, or both. Your AI app calls ads.serve. Adgentek handles everything else.

// 1. Add the remote server to your MCP client config { "mcpServers": { "adgentek-ads": { "url": "https://mcp.adgentek.ai/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } // 2. Call ads.serve with conversation context // 3. Render the response. Tracking is fully automatic.
70%

Higher ROAS vs. traditional channels on conversational AI inventory

Full

Ad server: bring your own demand sources or use Adgentek's

9

Intent classification buckets, matched automatically at request time

0

Raw conversation data transmitted to advertisers. Derived signals only.

Getting Started

Live in three steps

1

Create your publisher account

Sign up at app.adgentek.ai, add an AI Surface, and get your API key and placement ID.

2

Add the MCP server config

One JSON block in your MCP client: the remote URL plus a Bearer header. No SDK, no package install.

3

Call ads.serve and earn

Pass conversation context. Render the response. All tracking is automatic, with no event calls required.

MCP Tools

Four tools. Complete ad server control.

AdsMCP exposes exactly the tools you need, from serving and prefetching to configuration and diagnostics.

ads.servePrimary

Serves a contextual ad based on conversation content. AdsMCP analyzes messages for topic, intent, sentiment, and depth, then matches and returns the highest-yield ad. Impressions, clicks, and conversions are tracked automatically.

messagessurfacesessionIduserKeyintentplacementCandidates

ads.prefetchPerformance

Batch-request multiple ads for caching and reduced latency at placement time. Pass an array of context objects, get back an array of ready-to-render ads. Cache results for up to 5 minutes.

batch[]messagessurfacesessionId

ads.configConfiguration

Returns your publisher configuration, slot definitions, and ad policies. Use this to check slot capabilities, adapt your integration, and enforce brand safety policies.

includeSlotsincludePoliciesincludeAnalytics

ads.diagnosticsDebug

Explains exactly why ads are or are not serving. Returns eligibility checks, per-ad filter reasons, and a full auction log including winner, total bids, and floor price.

checkEligibilityincludeAuctionLogmessagessurface
Full Ad Server

Bring your own ads, or use ours

AdsMCP is not a demand source with an MCP interface bolted on. It is a complete ad server, purpose-built for conversational AI surfaces and flexible enough to serve as the single monetization layer for your entire app. Yield is optimized automatically across every source, with no manual prioritization required.

Adgentek's live demand

Established relationships across programmatic, performance, and direct channels, with more added continuously. Start earning from your first impression.

Your direct-sold campaigns

Upload advertiser deals and serve them through the same ads.serve call, alongside network demand.

Additional ad sources

Connect your own demand partners alongside Adgentek's and let the server optimize yield across all of them.

Ad server, not just a network

Full ad serving infrastructure: trafficking, targeting, capping, pacing, and reporting, hosted and managed by Adgentek.

Intent-aware matching

Nine-bucket intent classification maps any conversation to a standardized signal automatically: purchase, transactional, comparison, research, and more.

Revenue share model

Publishers receive a share of net ad revenue on every impression. No upfront costs, no minimum traffic requirements.

Privacy

User conversations stay private. Full stop.

Raw conversation content never leaves your application and is never shared with advertisers, demand partners, or third parties. Ad matching runs on derived signals only: the minimum information required to serve a relevant ad.

What advertisers receiveWhat stays in your app
IAB content categoryFull conversation content
Intent classificationUser messages
Keyword themesSession context

Conversations never shared beyond Adgentek. User conversation content is not stored, forwarded to demand partners, or used for cross-publisher profiling.

Compliant by design. AdsMCP's signal architecture aligns with emerging AI platform data policies and consumer privacy expectations, built in from the foundation rather than added as a layer.

Derived signals only, always. Whether matching on contextual or audience signals, only derived classifications reach demand partners, never raw conversation data. See intent-native targeting for how the signal model works.

Ready to monetize your AI app?

Create your publisher account, get your API key, and start serving contextual ads. Integration takes minutes. Live demand from day one.