
Campaign Manager 360 MCP Server
Manage Google Campaign Manager 360 entities, Floodlight conversions, and async reports from your agent when you operate display and measurement stacks.
Overview
CM360 MCP is an MCP server for the Grow phase that lets agents manage Campaign Manager 360 CRUD, Floodlight tracking, async reporting, and targeting.
What is this MCP server?
- Campaign Manager 360 CRUD exposed through MCP tools
- Floodlight activity and conversion tracking management
- Async reporting workflows for campaign performance
- Targeting configuration accessible to agents
- npm @cesteral/cm360-mcp v1.1.0 plus optional hosted streamable-http endpoint
- Server version 1.1.0
- npm package @cesteral/cm360-mcp
- Documented capabilities: CRUD, Floodlight, async reporting, targeting
What problem does it solve?
Operators living in CM360 and spreadsheets struggle to let an agent safely adjust tags, entities, or reports without custom Google API glue code.
Who is it for?
Indie developers and lean ad-ops teams with CM360 access who want agent-driven reporting and entity maintenance.
Skip if: Builders with no Google Marketing Platform setup or who only run single-channel Meta or TikTok ads.
What do I get? / Deliverables
Once configured, your agent can orchestrate CM360 management and reporting through MCP instead of one-off API scripts.
- Agent-managed CM360 entity updates
- Floodlight and targeting changes initiated via MCP
- Async performance reports surfaced to the agent session
Recommended MCP Servers
Journey fit
CM360 is used post-launch to track campaigns and conversion tags, aligning with grow-phase measurement and optimization. Analytics fits Floodlight tracking review and async reporting more than initial channel selection in launch.
How it compares
Google CM360 API MCP bridge, not a landing-page generator or SEO content workflow.
Common Questions / FAQ
Who is CM360 MCP for?
It is for developers who use Campaign Manager 360 and want coding agents to handle CRUD, Floodlight, reports, and targeting via MCP.
When should I use CM360 MCP?
Use it during grow and analytics work when campaigns are active and you need recurring async reports, tag checks, or structural updates from an agent.
How do I add CM360 MCP to my agent?
Add @cesteral/cm360-mcp via npm for stdio with Google API credentials, or deploy the server and configure your client with https://{host}/cm360-mcp/mcp as the streamable-http remote.