4 ways to connect Microsoft Ads to Claude in 2026 (the easy way)

Prerequisites

• A Porter Metrics account with your Microsoft Ads account connected (free tier is enough to try it end-to-end)
• A Claude account — the free plan works for Claude Web; a Pro subscription is needed for Claude Code and Desktop MCP features
• Admin or standard access to the Microsoft Ads accounts you want to connect

Connect Microsoft Ads to Claude with MCP

For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Microsoft Ads.

Four reasons MCP wins for Microsoft Ads:

The full setup takes under 5 minutes and breaks into three moves: connect Microsoft Ads to Porter, point Claude at the Porter MCP, and ask your first question.

1. Connect your Microsoft Ads data to Porter

Porter sits between Microsoft’s Advertising API and Claude. It handles OAuth, rate limiting, pagination and all the plumbing so Claude only ever sees clean, structured data.

Optional: enable automatic BigQuery storage if you’re connecting multiple accounts with large data volumes. This keeps Claude’s responses fast even at scale.

2. Connect the MCP to Claude

Porter’s MCP URL is what you paste into Claude. Once added, Claude can query Microsoft Ads data on demand in any conversation.

Go to claude.ai and click the + icon in the chat input to open the tools menu.

In the menu that opens, hover over Connectors and click Manage connectors.

In the Connectors panel, click the + button at the top of the list to start adding a new connector.

Pick Add custom connector from the dropdown that appears.

A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.

In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.

Click Add at the bottom right of the dialog. Claude opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.

Once the authorization finishes, you’ll see Porter’s read-only tools appear in the connectors panel. You’re ready to start asking questions.

For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.

3. Start building questions and dashboards

With Porter connected, open a new Claude chat and ask anything about your Microsoft Ads in plain English. Claude calls Porter behind the scenes, pulls live data from Microsoft, and answers with tables, charts, or summaries.

Try one of these to verify the setup is working:

For a full catalogue of copy-paste prompts organized by use case (performance, fatigue, budget, agency, B2B, e-commerce, cross-channel), jump to the prompts section below.

Alternative ways to connect Microsoft Ads to Claude

MCP is the path we just walked through — and the one we recommend for most marketers. But it’s not the only way to get Microsoft Ads data in front of Claude. The most common alternatives are Microsoft Ads’s direct API (or its official MCP if it has one), a live Google Sheets bridge, and BigQuery for scale. Each has its trade-offs — pick the one that fits how your team already works.

• 🔌 Microsoft Ads’s direct API (or official MCP) — Talk to Microsoft’s Advertising API yourself, or install Microsoft Ads’s native MCP if one exists. Maximum control, but you handle auth, rate limits and pagination — and you only get one source.
• 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
• 🗄️ Google BigQuery — For large accounts or agencies running multi-account analysis. BigQuery aggregates; Claude only queries pre-built summaries.

Via Microsoft Ads’s direct API (or official MCP)

If you’re building a product around Microsoft Ads — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Microsoft’s Advertising API yourself, or installing an official Microsoft Ads MCP (if one exists). Microsoft doesn’t ship an official MCP for Advertising yet, so this means writing API calls directly in Claude Code or in your own scripts. You’ll need to follow Microsoft’s rate limits & quotas where applicable. Either way, you skip Porter entirely and call Microsoft from your own code or from Claude Code with raw HTTP requests.

Via Google Sheets (live Sheet or manual CSV)

If your team already lives in Google Sheets — or you want a paper trail before Claude touches anything — feed Microsoft Ads into a Sheet, then let Claude read the Sheet. You can automate the Microsoft Ads → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Microsoft Advertising dashboard for static analysis.

Via Google BigQuery (for scale)

This is the path most people overlook — and it’s the one that saves you when your Microsoft Ads account gets serious. A single large advertiser or an agency managing 10+ accounts will hit API rate limits and latency problems querying Claude directly. Claude will literally tell you it’s taking too long or timing out on big pulls.

BigQuery fixes that. You load Microsoft Ads data into BigQuery tables on a schedule, then connect BigQuery to Claude — either through a BigQuery MCP or via Claude Code with SQL queries. Instead of asking Claude to pull raw Microsoft Ads data, you let BigQuery aggregate into small, optimized tables, and Claude only queries the summarized output. Scale problem solved.

Connecting Microsoft Ads to Claude Code

Most marketers lump Claude and Claude Code together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Microsoft Ads data seriously.

What Claude Code unlocks that Claude alone cannot

This is where the MCP ecosystem pays off most. Because Claude Code can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.

🛠️ Build your own budget management app

Feed Claude Code your Microsoft Ads targets and goals — CPA goals, daily budgets, ROAS thresholds — and ask it to generate a custom ROI dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load.

🔍 Full competitor + performance monitoring

Combine your own Microsoft Ads performance from Porter with competitor landing pages and live ads scraped via Firecrawl. Claude Code stitches both into a weekly competitive intelligence report — your numbers next to their creative angles and pricing, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning.

📚 Internal marketing wiki with live metrics

Use Airtable or Notion as the schema, Porter as the data source. Claude Code keeps every page populated with current Spend, Conversions, and Ctr for every account — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account.

🔔 24/7 alerts on spend, Ctr, and quality drops

A Claude Code routine on cron pulls Microsoft Ads via Porter, evaluates thresholds — Ctr drops below 1%, daily spend spikes 2× the trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look.

Use cases — what you can actually do once Microsoft Ads is connected to Claude

Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Microsoft Ads data — from simple Q&A to full client-facing workflows.

1. Chat and ask questions directly

The simplest use case — and still the one 80% of marketers start with. Open Claude, ask a question, get an answer grounded in live data.

It’s the fastest way to replace a daily Microsoft Advertising dashboard check-in. But chat is table stakes — the interesting use cases come next.

2. Blend Microsoft Ads with your revenue data (Stripe, HubSpot, Shopify)

This is where a 360° view gets real. When you connect Microsoft Ads and your revenue source (Stripe for SaaS, HubSpot CRM for B2B, Shopify for e-commerce), Claude can map ad campaigns to actual closed-won deals or purchases — using UTMs, campaign names, and timestamps — and give you attribution that no platform-side number can.

Claude handles the UTMs, campaign names, and timestamps mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.

3. Automated alerts and notifications on Slack or Gmail

With Claude Code you can turn Microsoft Ads monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Claude Code scheduled task that pulls performance every morning and pings you only when something actually needs attention.

No dashboards, no daily check-ins. The report comes to you — and only when it matters.

4. Client-ready presentations with live data (Gamma, HTML, PDF)

A common agency pain: you send clients a Data Studio link, Looker breaks, the client panics — and you spend an hour explaining a broken dashboard. With Claude you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.

The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.

Microsoft Ads fields and metrics you can query with Claude

Prompts you can copy-paste today

1. For agencies

Use these when you’re managing multiple client accounts and need fast, client-ready answers.

2. For B2B marketers

Use these when you’re running lead-gen campaigns and care about quality, not just volume.

3. For e-commerce teams

Use these when you’re tracking Revenue, ROAS, and shopping campaign performance.

4. Cross-channel

Use these when you want to compare Microsoft Ads against other paid channels in one conversation.

Limits, safety, and best practices for Microsoft Ads via Claude

While Microsoft Ads does not ban accounts for legitimate API usage, enforcement is real and aggressive for policy violations. The risk for marketers using MCP integrations is not account suspension — it’s throttling and data disruption. A marketing agency running multi-tenant reporting through a single app registration can hit rate ceilings within minutes, causing Claude to return stale or incomplete campaign data. The real cost is not a banned account; it’s lost optimization windows and decisions made on partial data.

Microsoft’s rate-limit enforcement is quota-based and account-wide, not tool-based. Microsoft doesn’t throttle accounts because you used Claude or an MCP. It throttles because of how the API was used: exceeding 40 queries per second, 60,000 method calls per minute, or 20,000,000 method calls per day. Read-only analysis within these thresholds is safe. Bursty traffic, unbatched parallel requests, or sharing a single app registration across multiple tenants is not. Persistent violations trigger Error Code 117 (CallRateExceeded), and continued abuse can lead to reduced rate limits or temporary suspension of API access within two business days.

The two ways to burn through your Microsoft Ads quota

After reviewing official docs and community threads, two patterns come up again and again.

Both behaviors trigger quota-based throttling. If you want to use Claude for Microsoft Ads safely, stay inside Microsoft’s documented limits, batch your requests, and isolate app registrations per tenant.

The 5-rule scaling protocol

Based on Microsoft’s documented rate limits and the behaviors that have actually caused throttling — not guesswork:

• Batch your requests. Microsoft counts each item in a batch as a separate method call, but the HTTP request itself counts as one against your 40 QPS limit. Batch up to 300 operations per request to maximize throughput. Microsoft Advertising API — Request Method Limits. Ignoring this burns through your 60,000 calls/minute quota 300x faster than necessary.

• Respect the 60-second cooldown after Error Code 117. When you exceed the per-minute call limit, Microsoft returns Numeric Error Code 117 with explicit instruction to reduce calls per minute and wait 60 seconds before retrying. Microsoft Advertising API — Request Method Limits. Retry storms without backoff will escalate throttling to account-level rate reduction.

• Do not exceed 25 requests every 20 seconds per app registration. This is the per-app hard ceiling. Microsoft Advertising API — Request Method Limits. If you manage multiple Microsoft Ads accounts through Claude, register separate Azure AD applications or use Porter’s native multi-account batching to stay under this threshold.

• Cap entity inputs to documented limits: 250 placements per profile, 100 profiles per member, 4,000 postal codes per profile. Microsoft Advertising API — Request Method Limits. Exceeding these does not trigger a ban, but causes silent truncation or partial write failures that leave campaigns misconfigured.

• Stay under the 20,000,000 method calls per day account ceiling. Microsoft Advertising API — Request Method Limits. For high-volume accounts with hourly reporting, this translates to roughly 833K calls per hour average — easily exceeded with unoptimized multi-year historical pulls. Porter MCP enforces daily budget tracking and warns before large date-range queries.

Frequently asked questions