Amazon DSP MCP Server
Wire Amazon DSP campaigns, audiences, and async performance reports into your agent when you run or automate programmatic ads for your product.
Overview
Amazon DSP MCP is an MCP server for the Grow phase that exposes Amazon DSP CRUD, async reports, targeting, and audience management to your agent.
What is this MCP server?
- Amazon DSP CRUD for campaigns and related entities via MCP
- Async report generation and retrieval for performance analysis
- Targeting and audience management tools for agent-driven optimization
- stdio npm package @cesteral/amazon-dsp-mcp and optional self-hosted streamable-http remote
- Version 1.1.0 from the mcp-open-advertising monorepo
- Server version 1.1.0
- npm package identifier @cesteral/amazon-dsp-mcp
- Supports stdio and streamable-http remote MCP transports
What problem does it solve?
Solo operators juggling DSP consoles and spreadsheets cannot quickly ask an agent to pull reports or tweak audiences without brittle custom scripts.
Who is it for?
Builders with Amazon DSP API access who want agent-assisted reporting, audience edits, and campaign maintenance for their SaaS or agency stack.
Skip if: Founders with no DSP account, no API credentials, or who only need organic SEO and content distribution.
What do I get? / Deliverables
After install, your agent can run DSP management and reporting workflows through MCP instead of manual console repetition.
- Agent-executed DSP CRUD and targeting changes
- Downloaded or summarized async performance reports
- Repeatable audience management without full console context switching
Recommended MCP Servers
Journey fit
Paid demand-side platforms are operated after launch when you measure spend and optimize acquisition, which maps to the grow phase. Analytics subphase covers CRUD plus async reporting and audience targeting review rather than one-off launch copy.
How it compares
Amazon Advertising API bridge via MCP, not a creative ad-copy skill or a self-serve social ads template.
Common Questions / FAQ
Who is Amazon DSP MCP for?
It is for developers and indie operators who manage Amazon DSP and want Claude Code, Cursor, or similar agents to handle CRUD, reports, targeting, and audiences.
When should I use Amazon DSP MCP?
Use it in the grow phase when you regularly pull async performance reports, adjust targeting, or automate DSP maintenance alongside your product analytics.
How do I add Amazon DSP MCP to my agent?
Install @cesteral/amazon-dsp-mcp from npm for stdio, configure Amazon Advertising API credentials per the GitHub repo, or deploy the server and set your MCP client remote URL to https://{host}/amazon-dsp-mcp/mcp.