Pipeboard
GuidesCampaign Manager 360 MCP
In development — looking for test accounts

Campaign Manager 360 MCP Server

Connect Claude, ChatGPT, or any AI tool to Campaign Manager 360 — Google’s ad server. Ask about your advertisers, campaigns, placements, Floodlight tags and cross-channel attribution in plain English.

What is the Campaign Manager 360 MCP?

The Pipeboard Campaign Manager 360 MCP (Model Context Protocol) Server connects AI assistants to the Campaign Manager 360 API. It covers what Campaign Manager 360 does: ad serving and trafficking (campaigns, placements, ads and creatives), tracking (Floodlight conversion tags and remarketing lists), and the reports that measure delivery and cross-channel attribution.

It is not a buying tool. Campaign Manager 360 serves and measures ads; it has no bids, budgets or auctions. To buy programmatic media, use the Display & Video 360 integration on your Connections page.

Campaign Manager 360 is in development

We are building this integration now. The Campaign Manager 360 card on your Connections page explains how to lend us a test account, and it connects only for accounts we have enabled — until then, the setup steps below will not be available to you. This guide documents what the MCP server does as each part ships.

Meta Ads, Google Ads, TikTok Ads, Reddit Ads, and Snap Ads are generally available on every plan today. Browse those guides →

Offer a test account

Getting Started

Once your account is enabled

1. Make sure the Google account you will connect has a Campaign Manager 360 user profile. A CM360 admin in your organization creates it; there are no separate API permissions — the profile’s role decides what Pipeboard can do.

2. Connect that Google account (you will review the access on Google’s consent screen):

pipeboard.co/connections/cm360 →

The Connect button works only for accounts we have enabled while the integration is in development — offer a test account above and we will switch it on.

3. Add the MCP server to your AI client:

https://cm360.mcp.pipeboard.co/

Use this URL as a Streamable HTTP MCP server. Authentication is handled through your Pipeboard session.

Tools available today

  • list_cm360_accounts — Every Campaign Manager 360 account (network) your connected Google accounts hold a user profile in — the account_id every other tool needs.
  • get_cm360_advertisers — The advertisers in one account, with status, advertiser group and Floodlight configuration.
  • get_cm360_campaigns — The campaigns in one account, optionally for given advertisers, with dates and archive state.
  • get_cm360_campaign — One campaign in full.

Coming next, in this order

  1. Trafficking reads — placements, ads, creatives, landing pages, sites, and the tags to send a publisher.
  2. Reporting and attribution — delivery and performance, Floodlight conversions, reach, and Path to Conversion.
  3. Tracking — Floodlight configurations, activities and their tags, and remarketing lists.
  4. Trafficking and tracking writes — campaigns, placements, ads, creatives and Floodlight activities, only ever at your request.

How we use your data

Pipeboard asks Google for two Campaign Manager 360 permissions — trafficking and reporting — and uses them only for the requests you make through your AI assistant. Each permission and what we do with it is listed on our Google integrations page.

You choose which accounts each connection exposes with Configure Access on the connection card, and an API token can be limited further to specific accounts.