Search Ads 360 MCP Server
Connect Claude, ChatGPT, or any AI tool to your Search Ads 360 advertisers. Ask about cross-engine search performance, spend, and conversions in plain English — no report builder, no query language to learn.
What is the Search Ads 360 MCP?
The Pipeboard Search Ads 360 MCP (Model Context Protocol) Server connects AI assistants like Claude, ChatGPT, and custom agents to the Search Ads 360 Reporting API. Instead of building a report in the SA360 interface or hand-writing queries, you ask a question in plain language and the assistant answers straight from your advertiser data.
It is built for enterprise search teams and agencies running Search Ads 360 across several engines and many advertisers — the accounts where the reporting surface is large enough that finding the right number is the actual work.
Reporting, plus offline conversions. Everything about campaigns is read-only: Search Ads 360 exposes no API to create, edit, pause or delete campaigns, ad groups, keywords, budgets or bids, so Pipeboard cannot change any of them. The one thing it writes is the offline conversions you ask it to upload or restate.
What you can do with it:
How Pipeboard uses your Search Ads 360 data
What we request, why, and what we never do with it
When you connect Search Ads 360, Pipeboard requests access through Google’s official OAuth consent screen. We only request the Google scopes needed to run the reporting tools described on this page, plus your basic account identity so we can show which Google account an advertiser belongs to. We use this access solely to fulfil the requests you (or your AI assistant, on your behalf) make.
The access we request, and why:
doubleclicksearchReading: Pipeboard lists the Search Ads 360 customers you can access, runs the reporting queries you ask for, and reads your custom column definitions and the API’s field metadata to build those queries. Writing: when you ask it to, it uploads offline conversions, restates their value after a refund or return, and marks a Floodlight activity’s uploads complete for a period. Those writes only add or correct conversion records you supply — Pipeboard cannot create, edit, pause or delete campaigns, ad groups, keywords, budgets or bids.
userinfo.emailIdentifies the connected account so we can label which Google login an advertiser belongs to. Important if you connect more than one Google account.
userinfo.profileDisplays the connected account name in your Pipeboard connections list so you can tell your connections apart.
Our commitments
- We never sell your Search Ads 360 data, and we never use it for advertising.
- Your data is used only to respond to the requests you or your AI assistant make — it is not used to train AI models.
- Pipeboard cannot change your campaigns, budgets, keywords or bids — Search Ads 360 exposes no API for that. The only writes are the offline conversions you ask it to upload or restate.
- You choose which advertisers are visible: Configure Access on your connection limits what the assistant can see, per Google account.
- You can disconnect Search Ads 360 at any time from your connections page, which revokes Pipeboard’s access.
- Pipeboard’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
See the shared Pipeboard for Google page for how every Google integration uses your data, plus full details in our Privacy Policy and Security pages.
Search Ads 360 is in limited early access
This integration is live for a small group of accounts while we roll it out. The Search Ads 360 card only appears on your Connections page once your account has been enabled — until then, the setup steps below will not be available to you.
Meta Ads, Google Ads, TikTok Ads, Reddit Ads, and Snap Ads are generally available on every plan today. Browse those guides →
Request early accessGetting Started
Set up in under 2 minutes, once your account is enabled
1. Sign up for a Pipeboard account:
pipeboard.co/auth/signup →2. Connect the Google account that can reach your Search Ads 360 advertisers (you’ll review and approve the access above on Google’s consent screen):
pipeboard.co/connections/search-ads-360 →During limited early access the Search Ads 360 card is not on this page yet unless your account has been enabled — request access above and we will switch it on.
3. Add the MCP server to Claude (or another MCP client):
https://search-ads-360.mcp.pipeboard.co/Use this URL as a Streamable HTTP MCP server in your client. Authentication is handled automatically through your Pipeboard session.
Connect to Your AI Tool
The Search Ads 360 MCP works with any MCP-compatible client. Add the server URL and start asking about your search performance in natural language.
Claude Pro / Max
Recommended- 1.Open claude.ai/customize/connectors
- 2.Click "Add custom connector"
- 3.URL:
https://search-ads-360.mcp.pipeboard.co/
Claude Code
CLI / VS CodeRun this command in your terminal:
claude mcp add --transport http pipeboard-search-ads-360 https://search-ads-360.mcp.pipeboard.co/Then type /mcp in Claude Code to authenticate with Pipeboard.
Alternative: use an API token for instant setup (no browser auth needed):
claude mcp add --transport http pipeboard-search-ads-360 https://search-ads-360.mcp.pipeboard.co/?token=pipeboard_...Get your token at pipeboard.co/api-tokens
Try these prompts
Account Discovery
"List my Search Ads 360 customers and tell me which ones are client accounts I can report on"
Spend Review
"For customer 123-456-7890, show me the top 10 campaigns by cost over the last 30 days with clicks and conversions"
Cross-Engine Comparison
"Compare clicks and cost by advertising channel for customer 123-456-7890 over the last quarter"
Custom Metrics
"What custom columns are defined on customer 123-456-7890, and can you report last month’s performance using them?"
What’s included
Accounts & discovery
- List every reachable customer across all connected Google accounts
- Tells you which are manager accounts and which are client advertisers
- Shows the Google account each customer is reachable through
- Manager routing is handled for you on every report
Reporting
- Campaign, ad group, and keyword performance
- Clicks, impressions, cost, and conversion metrics
- Any date range, including relative ranges like the last 30 days
- Paginated results so large reports arrive in readable pages
Offline conversions
- Upload conversions that closed off-site, attributed by gclid or keyword
- Restate value after a refund, return or discount — or retract a conversion
- Mark a Floodlight activity complete for a period, including empty runs
- Duplicate uploads are rejected, not double-counted
Query building
- Field metadata: what exists on each resource and its data type
- Which fields are selectable, filterable, and sortable
- Custom column definitions per advertiser
- Validate a report query before running it
Access control
- Campaigns, budgets, keywords and bids cannot be changed — no API for it
- Configure Access picks which advertisers are visible per connection
- API tokens can be scoped to specific advertisers
- Read-only API tokens cannot upload or restate conversions
- Every report names the advertiser it came from
Best Practices
- List your customers first, then pass the customer id on every report — manager accounts hold no metrics of their own
- Ask for a specific date range; relative ranges like “the last 30 days” work and keep comparisons consistent
- Remember that cost arrives in micros — divide by 1,000,000 for currency (the assistant normally does this for you)
- Let the assistant look up field metadata rather than guessing field names; invalid fields are rejected by the API
- Narrow reports with filters and limits instead of pulling everything and summarizing afterwards
- Use Configure Access to hide advertisers you do not want an assistant to see, per connected Google account