Developers are spending more time talking to AI agents than browsing documentation sites. Claude, Cursor, Windsurf, Copilot - these are the new surfaces where developers discover tools and make decisions.
If you market developer tools, this shift matters. The old playbook (Google Ads, conference booths, banner sponsorships) still works, but there's a new channel opening up: contextual advertising inside AI agent workflows.
Here's how it works and why it's different from everything else.
The Problem With Developer Advertising Today
Most developer advertising is interruptive. Banner ads on Stack Overflow. Sponsored search results on Google. Newsletter sponsorships. Conference booths.
These channels share a weakness: they compete for attention in moments when the developer isn't doing the thing your product helps with. They're browsing, reading, or socializing - not building.
AI agents change this. When a developer asks their coding agent "what database should I use for this project?" or "find me an auth library," they're expressing real-time intent. That's the moment your product is relevant.
How Agent-Mediated Advertising Works
MCP (Model Context Protocol) is the standard that connects AI agents to external tools. There are 10,000+ MCP servers in production, used by ChatGPT, Claude, Cursor, and others.
Some of these servers handle queries where product recommendations are natural:
- Search tools that help agents find services or APIs
- Comparison tools that evaluate options across categories
- Infrastructure tools that suggest hosting, databases, or deployment targets
- Development tools that recommend libraries, SDKs, or frameworks
When a developer's agent queries one of these tools, the response can include sponsored results alongside organic ones. Labeled clearly. Relevant to the actual query. Not a popup or a banner - a contextual recommendation at the point of decision.
Why This Is Different
Intent-based, not impression-based. Traditional display ads charge per thousand views. Most viewers aren't in a buying moment. Agent-mediated ads fire when someone is actively looking for a solution. Every impression carries intent.
Agent-mediated trust. The developer trusts their AI agent. If the agent surfaces your tool as a relevant option (clearly labeled as sponsored), that carries more weight than a sidebar banner.
Privacy by design. No cookies, no tracking pixels, no personal data. Targeting is based on the query context (what the agent is asking about), not the user's browsing history. This is where the industry is heading anyway - you might as well build for it now.
Measurable outcomes. You can track: was the ad shown (impression), did the agent present it to the user (click), did the user act on it (conversion). Clean funnel, no attribution guesswork.
Who's Already Doing This
This isn't theoretical. Several companies are building the infrastructure:
- Amazon Ads launched an MCP server in open beta, letting agents query their ad inventory programmatically
- Dstillery shipped DS-1, an MCP-native audience builder integrated with The Trade Desk
- PubMatic built AgenticOS for agent-to-agent advertising orchestration
- IAB Tech Lab is releasing "agentified" standards for the advertising industry in 2026
The Ad Commerce Protocol (AdCP) is emerging as an open standard for agent-to-agent ad execution. The MCP Dev Summit (April 2-3, NYC) has sessions specifically on advertising standards.
What a Campaign Looks Like
For a developer tool company, the setup is straightforward:
Define your targeting. What queries is your product relevant for? A database company targets queries about data storage, persistence, scaling. An auth provider targets queries about authentication, identity, security.
Set your budget. Pay per click (CPC) or per conversion (CPA). No minimum spend. You only pay when an agent actually presents your tool to a developer.
Provide your creative. Not a banner. A structured product listing: name, one-line description, link, and the query categories where you want to appear.
Measure results. Track impressions, clicks, and conversions. Optimize targeting based on which query contexts convert best.
The revenue split on the supply side is typically 70/30 (MCP server builder keeps 70%). This means server builders are incentivized to integrate ads, which grows the network of surfaces where your product can appear.
When to Consider This Channel
This channel makes sense if:
- Your product solves a problem developers encounter while building (not just while browsing)
- You're comfortable with contextual targeting (no personal data, no retargeting)
- You want to reach developers at the moment they're evaluating options
- Your product has a clear, short value proposition (one line, not a paragraph)
It probably doesn't make sense yet if you need massive scale. The MCP ad ecosystem is early. Thousands of servers, not millions. But early movers get lower CPCs and first-mover positioning in a channel that's growing 85% month-over-month.
Getting Started
If you run marketing for a developer tool company and want to test this channel, there are a few ways in:
- agentic-ads is an open-source ad network built specifically for MCP tools. You can register campaigns, set targeting by keyword context, and pay per click or conversion.
- Amazon's MCP ad server is in open beta for their existing advertiser base.
- Several MCP marketplace platforms (Apify, Smithery) are building native ad placement features.
The market is early enough that a small test budget goes a long way. And unlike display ads, you'll know exactly which developer queries led to which outcomes.
Building something in the MCP ad space? I'd like to hear about it.
Top comments (0)