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

TL;DR

To connect TikTok Ads to Claude via MCP: copy mcp.portermetrics.com/mcp, go to Claude.ai, open Connectors → Manage connectors → Add custom connector, paste the URL, and sign in. From there, ask Claude anything about your TikTok Ads campaigns in plain English.

Once connected, you can automate your TikTok Ads reporting and analysis — ask questions about your data, build dashboards, trigger alerts, or ship client-ready reports like the one below.

Prerequisites

• A Porter Metrics account with your TikTok 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 TikTok Ads ad accounts you want to connect

Connect TikTok 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 TikTok Ads.

MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Claude Code and others access and use external APIs — the things that make tools like TikTok Ads work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.

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

1. Connect your TikTok Ads data to Porter

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

Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.

Connect your TikTok Ads Developer Token / API access. In Porter, click Create → pick Claude as the destination → select TikTok Ads as the source → sign in with TikTok to grant access to your ad accounts.

Select your ad accounts. Choose the TikTok Ads ad accounts you want Claude to query. When you select multiple ad accounts under a single connection, Porter automatically blends their data together so you can query them as one.

Optional: enable automatic BigQuery storage if you’re connecting multiple ad 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 TikTok 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 TikTok Ads in plain English. Claude calls Porter behind the scenes, pulls live data from TikTok, 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 TikTok 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 TikTok Ads data in front of Claude. The most common alternatives are TikTok 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.

• 🔌 TikTok Ads’s direct API (or official MCP) — Talk to TikTok’s Marketing API yourself, or install the official TikTok Ads 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 ad accounts or agencies running multi-account analysis. BigQuery aggregates; Claude only queries pre-built summaries.

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

If you’re building a product around TikTok Ads — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to TikTok’s Marketing API yourself, or installing the official TikTok Ads MCP (if one exists). TikTok doesn’t ship an official MCP yet, so this means writing API calls directly in Claude Code or in your own scripts. You’ll need to follow TikTok’s rate limits & quotas and request a Developer Token / API access where applicable. Either way, you skip Porter entirely and call TikTok 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 TikTok Ads into a Sheet, then let Claude read the Sheet. You can automate the TikTok Ads → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from TikTok Ads Manager for static analysis.

Read the full Sheets tutorial →

Via Google BigQuery (for scale)

This is the path most people overlook — and it’s the one that saves you when your TikTok Ads ad account gets serious. A single large advertiser or an agency managing 10+ ad 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 TikTok 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 TikTok Ads data, you let BigQuery aggregate into small, optimized tables, and Claude only queries the summarized output. Scale problem solved.

Read the full BigQuery tutorial →

Connecting TikTok 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 TikTok Ads data seriously.

Claude is a chat interface. You ask a question, Claude pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.

Claude Code is Claude running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for TikTok Ads, a whole category of work becomes possible.

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 Stack: Porter MCP + Vercel MCP (or Cloudflare Pages, Netlify) Feed Claude Code your TikTok 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. Best for: agencies that want white-label client dashboards without Looker or Data Studio dependencies.

🔍 Full competitor + performance monitoring Stack: Porter MCP + Firecrawl MCP Combine your own TikTok Ads performance from Porter with competitor landing pages and live ads from the Meta Ad Library 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. Best for: in-house teams that need market context, not just internal numbers.

📚 Internal marketing wiki with live metrics Stack: Porter MCP + Airtable MCP (or Notion MCP) Use Airtable or Notion as the schema, Porter as the data source. Claude Code keeps every page populated with current spend, CPA, and ROAS for every ad account — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account. Best for: agencies and ops teams onboarding analysts or rotating account managers frequently.

🔔 24/7 alerts on spend, CTR, and quality drops Stack: Porter MCP + Slack MCP (or Gmail MCP) A Claude Code routine on cron pulls TikTok 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. Best for: any team that’s ever discovered a problem 48 hours too late because nobody opened the report.

Bottom line: Claude is for quick questions and ad-hoc dashboards. Claude Code is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.

Use cases — what you can actually do once TikTok 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 TikTok 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 TikTok Ads Manager check-in. But chat is table stakes — the interesting use cases come next.

2. Blend TikTok Ads with your sales data (Stripe, HubSpot, Shopify)

This is where a 360° view gets real. When you connect TikTok 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 UTM 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 TikTok 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.

TikTok Ads fields and metrics you can query with Claude

Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives Claude access to 597 TikTok Ads metrics across every reporting level, plus breakdowns by audience, placement, device, and geography. And the same MCP URL also unlocks 25+ other sources — so Claude can blend TikTok Ads with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.

Prompts you can copy-paste today

1. For agencies managing multiple TikTok accounts

Use these when juggling multi-client campaigns, spotting creative fatigue across 4–7 day cycles, and shipping white-label reports.

2. For B2B marketers running lead gen

Use these when optimizing lead-gen campaigns with form fills, registrations, and lookalike audiences.

3. For e-commerce teams selling on TikTok Shop

Use these when tracking TikTok Shop onsite purchases, ROAS, and creative performance for product campaigns.

4. Cross-channel: TikTok Ads + Meta + Google

Use these when comparing TikTok performance against Meta and Google Ads in a single conversation.

How to use Claude Code for TikTok Ads without getting banned

TikTok’s 2025-2026 compliance-driven rebuild of its advertising infrastructure created real data-quality pain for marketers relying on API-reported metrics. During the transition, historical conversion data became unreliable, creative review queues lengthened, and targeting/delivery systems experienced temporary disruptions. For a performance marketer spending €1,000+/month, this meant pipeline forecasts were off, ROAS calculations were stale, and budget pacing decisions were made with incomplete data — not a “ban” scenario, but a “broken data” scenario that cost real money in misallocated spend.

TikTok’s enforcement is rate-throttling based, not tool-based. TikTok does not ban accounts because you used Claude or an MCP server. It throttles (HTTP 429) or restricts (HTTP 403) because of how the API was used: excessive request volume, spam-like patterns, or unapproved access scopes. Read-only reporting access within reasonable request volumes is safe. Bursty parallel requests, write operations at scale, or scraping-like behavior is not. TikTok’s primary programmatic interface for ads — the Commercial Content API — has extremely restrictive access requirements and no openly documented rate limits for general developers, meaning most “TikTok Ads API” integrations operate through partner-approved or whitelisted endpoints rather than a fully public API.

The two patterns that lead to inaccurate TikTok Ads reports

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

1. Relying on real-time API data for same-day optimization decisions. TikTok Ads reporting data can experience delays of up to 24 hours for some metrics, and during platform transitions (like the 2025-2026 rebuild), historical conversion data gaps have been documented. Marketers who treat API-reported numbers as ground truth for intraday budget shifts or creative pauses make decisions on incomplete data. The consequence is not a ban — it’s misallocated spend and false-negative performance signals. Source: TikTok for Business compliance rebuild documentation, 2025-2026.

2. Assuming write access parity with read access. Third-party MCP servers and open-source connectors often advertise “campaign management” (CRUD operations) but may only support GET operations for campaigns and ad groups, with CREATE/UPDATE either undocumented or unsupported. Marketers who build automated workflows assuming full write capabilities discover gaps only after deployment, breaking automation pipelines. Source: competitor analysis — AdsMCP repository lists CREATE/UPDATE endpoints without documented parameter requirements.

Both behaviors trigger data quality degradation and rate throttling. If you want to use Claude for TikTok Ads safely, stick to read-only reporting within reasonable request volumes and treat API data as “yesterday’s truth,” not real-time gospel.

The 5-rule safety protocol

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

• Treat API data as “yesterday’s truth,” not real-time gospel. TikTok’s reporting infrastructure has documented 24-hour delays for some metrics during platform transitions. Consequence if ignored: intraday budget shifts based on incomplete data burn spend on underperforming creatives. Porter MCP handles this by surfacing data freshness timestamps and flagging metrics known to have delayed availability.

• Cap concurrent API requests to 10 or fewer per app. Community-documented third-party MCP implementations cite 10 concurrent requests as a safe ceiling to avoid HTTP 429 throttling. Consequence if ignored: throttled requests, incomplete data syncs, and broken automation loops. Porter MCP enforces connection-level request batching and automatic backoff to stay within safe concurrency ranges.

• Limit request volume to 1,000 per hour per app. This number appears in third-party MCP documentation (AdsMCP) but is not confirmed in publicly available official TikTok docs. Consequence if ignored: rate limiting (HTTP 429) that pauses data retrieval for minutes to hours. Porter MCP implements request pacing and queue management to distribute load evenly across the hour.

• Validate that write operations are fully supported before automating them. Not all developer accounts or API apps have write permissions for campaigns, ad groups, or ads. Consequence if ignored: automation scripts fail silently or partially, leaving campaigns in inconsistent states. Porter MCP’s native connector operates with pre-validated scopes — read-only by default, with write capabilities explicitly enabled and tested per account.

• Use location IDs (not country codes) for all geo-targeting API calls. TikTok’s targeting API requires specific location IDs rather than ISO country codes. Consequence if ignored: targeting parameters fail validation, campaigns don’t serve to intended audiences, and API errors block campaign creation. Porter MCP maps country/region selections to TikTok’s canonical location ID taxonomy automatically.

What Porter MCP does differently: it enforces these safeguards at the platform level. Porter’s native TikTok Ads connector is read-only by default, with optional write scopes explicitly enabled per account. Request volume is automatically paced to avoid throttling. Data freshness timestamps are surfaced for every metric pulled. Geo-targeting parameters are automatically mapped to TikTok’s location ID taxonomy. Per-account batching prevents cross-account quota bleed. That’s the behavior TikTok’s automated systems handle gracefully — predictable, moderate-volume, read-predominant API usage from a single whitelisted partner app.

Frequently asked questions