Unified advertising automation protocol built on Model Context Protocol (MCP)
AdCP revolutionizes advertising automation by providing a single, AI-powered protocol that works across all major advertising platforms.
Visit adcontextprotocol.org for full documentation.
Ad Context Protocol (AdCP) is an open standard for advertising automation that enables AI assistants to interact with advertising platforms through natural language. Built on the Model Context Protocol (MCP), AdCP provides:
- 🔌 Unified Advertising API - Single interface for all advertising platforms
- 🤖 AI-Powered Automation - Built for natural language campaign management
- 📊 Cross-Platform Analytics - Standardized reporting across all platforms
- 🔓 Open Standard - No vendor lock-in, community-driven development
- ⚡ Programmatic Ready - Designed for modern ad tech workflows
Instead of navigating complex interfaces:
"Find audience signals of premium sports enthusiasts who would be interested in high-end running shoes, and activate them on Scope3."
The AI assistant handles:
- Signal discovery across platforms
- Transparent pricing comparison
- Direct activation on decisioning platforms
Discover and activate data signals using natural language.
- Natural Language Discovery: "High-income millennials interested in sustainable fashion" (audience signal)
- Contextual Signals: "Premium automotive content with high viewability"
- Multi-Dimensional: Combine geographical, temporal, and behavioral signals
- Multi-Platform Activation: Deploy across DSPs and data platforms
- Transparent Pricing: CPM and revenue share models
- Real-time Status: Track activation and deployment progress
Curate media inventory based on context and brand safety requirements.
Execute and optimize media buys programmatically across platforms.
Implement AdCP to enable AI-powered workflows for your customers:
- Review the Specification: Signals Protocol
- Implement MCP Server: Check out the reference implementations
- Test Your Implementation: Use the validation test suite
Use AdCP-enabled platforms with your AI assistant:
- Check Platform Support: See which platforms support AdCP
- Configure Your AI: Connect AdCP-enabled platforms to Claude, GPT, or other assistants
- Start Using: Describe your marketing objectives in natural language
adcontextprotocol/
├── mintlify-docs/ # Mintlify documentation (docs.adcontextprotocol.org)
│ ├── docs/ # Protocol documentation
│ │ ├── signals/ # Signals protocol
│ │ ├── media-buy/ # Media Buy protocol
│ │ └── creatives/ # Creative protocol
├── server/ # Express server
│ ├── src/ # TypeScript server code
│ └── public/ # Static HTML pages (homepage, registry UI)
├── static/ # Static assets
│ └── schemas/ # JSON schemas
├── registry/ # Agent registry
│ ├── creative/ # Creative agents
│ ├── media-buy/ # Media buy agents
│ └── signals/ # Signal agents
└── README.md # This file
Join our working group to help shape the future of advertising protocols:
- Monthly Meetings: First Wednesday of each month
- GitHub Discussions: Join the conversation
- Mailing List: [email protected]
We welcome contributions from:
- Platform Providers: Implement and improve protocols
- Agencies & Advertisers: Share use cases and feedback
- Developers: Contribute code, documentation, and examples
- Industry Experts: Help define standards and best practices
See CONTRIBUTING.md for guidelines.
- Reference Implementation: Complete MCP server example
- Scope3: Full Signals Activation Protocol support
- More Coming: Additional platforms implementing Q1 2025
This repository runs a unified Express server that serves everything from a single process:
- 🏠 Homepage at
/ - 🤖 Agent Registry at
/registry- Browse and test all AdCP agents - 📋 AdAgents Manager at
/adagents- Validate and create adagents.json files - 📄 JSON Schemas at
/schemas/* - 🔧 REST API at
/api/* - 📡 MCP Protocol at
/mcp
# Install dependencies
npm install
# Start unified server (HTTP mode)
npm start
# Start in MCP mode (stdio)
npm start:mcp
# Run tests
npm test
# Build TypeScript
npm run build
# Start Mintlify docs (separate)
npm run start:mintlifyThe server runs on port 3000 by default. Visit:
- http://localhost:3000 - Homepage
- http://localhost:3000/registry - 🤖 Agent Registry (browse and test AdCP agents)
- http://localhost:3000/adagents - 📋 AdAgents.json Manager (validate and create adagents.json files)
- http://localhost:3000/schemas/v1/index.json - Schema Registry
- http://localhost:3000/api/agents - REST API
PORT- Server port (default: 3000)NODE_ENV- Environment (development|production)MODE- Server mode (http|mcp)
FROM node:18
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build
ENV NODE_ENV=production
EXPOSE 3000
CMD ["npm", "start"]The Ad Context Protocol specifications are licensed under Apache 2.0.
- General Inquiries: [email protected]
- Technical Support: [email protected]
- Security Issues: [email protected]
- Partnership: [email protected]
- Build unified advertising automation tools
- Integrate with multiple platforms through single API
- Enable AI-powered advertising workflows
- Create MCP-compatible advertising servers
- Automate campaign management across all platforms
- Use natural language for advertising operations
- Get unified analytics and reporting
- Reduce integration and maintenance costs
- Expose inventory through standardized protocol
- Enable AI assistant integration
- Participate in automated advertising ecosystem
- Implement once, work with all AI tools
advertising automation, programmatic advertising API, MCP advertising integration, AI advertising workflows, unified advertising platform API, advertising protocol standard, Model Context Protocol advertising, cross-platform advertising automation
- Website: adcontextprotocol.org
- API Documentation: Advertising Automation API
- MCP Integration: MCP Advertising Guide
- Specifications: Signals Protocol RFC
- Discussions: GitHub Discussions
- Issues: Report Issues
Built with ❤️ by the advertising technology community.