TikTok Ads MCP Server: How to Connect an AI Agent

TikTok announced its Ads MCP server at TikTok World in May 2026, shipped it quietly between June 30 and July 3, and then something odd happened: the guides didn't update. Articles written in early June still rank, still say "announcement, not product," and they are now wrong twice over: the endpoints are live and the documentation exists.

There is a mechanical reason for the confusion, and it is worth stating because it explains most of what you will read elsewhere: the official docs are a JavaScript-rendered app. A plain HTTP fetch, which is what most scrapers, AI crawlers, and quick-take bloggers use, returns an empty page with a title. We rendered the portal in a real browser and probed both MCP endpoints directly (both returned a live auth challenge on August 12, 2026, and again when we re-checked on October 6). As far as we can find, no independent practitioner write-up of the official server exists yet. This is that write-up, minus the parts we could not verify, which are labeled.

The two endpoints, and which to pick

The official server is remote-only, at two URLs on business-api.tiktok.com/open_mcp/:

• tt-ads-mcp-flat (Full Disclosure): all ~400 tools load at connection. TikTok's docs recommend this one for Claude.
• tt-ads-mcp-layer (Progressive Disclosure): ~40 core tools load up front, the rest on demand.

Take the vendor recommendation with history attached: TikTok's own docs carry an incident note that in early July Claude's tool management omitted tools beyond 256 by default, characterized by TikTok as fixed on July 20. Four hundred tools is also simply a heavy context load. Unless your agent genuinely needs the long tail at connection time, the layer endpoint is the saner default on any client.

Connecting: no developer account, no API key

This is the part every stale guide gets wrong. The official flow requires only a TikTok for Business account: explicitly no developer registration, no app creation, no token generation. Configuration is a standard remote MCP entry:

{ "mcpServers": { "tiktok-ads": { "url": "https://business-api.tiktok.com/open_mcp/tt-ads-mcp-layer" } } }

Start the client, follow the browser authorization with your TikTok for Business login, approve, done. If a guide tells you to create a developer app at business-api.tiktok.com and mint a long-term access token, it is describing the community path (below) or is out of date.

Two operational facts the connect page undersells. Authorization lasts 30 days, and re-auth is required with the same account, so your monthly automation will break silently on schedule. And permission granularity is undocumented: no scope picker, no documented read-only grant, nothing we could verify about how Business Center roles constrain the agent.

What your agent can now touch

The tool table spans campaign, ad group and ad CRUD, reporting with async report runs, creative upload, and budget and payment-adjacent tools. The CRUD side includes Upgraded Smart+ (smart_plus_campaign_create, smart_plus_ad_create) and GMV Max (campaign_gmv_max_create, gmv_max_report_get). Rate limits are documented at 3 QPS per tool per user, with Smart+ ad writes throttled to one operation per 5 seconds per ad.

Per-tool parameter documentation deliberately does not exist on the MCP pages: each tool wraps a Marketing API v1.3 endpoint, so the schema source is the Marketing API reference, or you ask the agent itself ("What parameters does smart_plus_ad_create need?"), which is the docs' own suggestion.

Read that tool list again from a risk angle: budget updates and payment tools are exposed alongside reporting. An authorized agent can move money, not just read dashboards. With no documented sandbox and no read-only mode, your guardrails today are one of: the community open-source servers (AdsMCP and ysntony: MIT-licensed, local, deliberately read-only), a paid managed connector that inserts a human-approval buffer before writes, or instruction-level discipline that you should treat as policy rather than enforcement.

The Agentic Hub, and the skill TikTok built for itself

The companion marketplace lives at ads.tiktok.com/apps_and_agents/agentic-hub, publicly browsable, launched June 30 with 14 partners including HubSpot, Wix and Constant Contact. Our August 12 snapshot counted 48 live skills: 18 built by TikTok (listed under TT4B and Byteplus) and 30 third-party. Skills use the open SKILL.md standard (ZIP with YAML-frontmatter SKILL.md plus README, 50MB cap), and publishing one, unlike connecting, does require developer registration, with a 5–7 business day review.

One listing deserves your attention if you make ad creative: TikTok itself ships a Byteplus skill that takes a reference ad and rewrites it into a new ad for your product on Seedance 2.0, carrying over hook, pacing and shot order with your product anchoring the visuals. The platform's own hub now contains the start-from-a-winner motion. That is worth pausing on: the largest short-video ad platform validated, in its own marketplace, that the way to make ad creative is to rebuild a proven video's formula around a new product.

The missing half of the loop

Everything the MCP server automates happens after a video exists. Campaigns, budgets, reporting, GMV Max: the agent can run all of it, but the creative is an input, and TikTok's in-hub answer is built to stay inside TikTok's walls.

Riffkit is the same motion outside TikTok's walls, and it plugs into the same assistant: add Riffkit's MCP connector to Claude or ChatGPT, or install the agent skill in Claude Code, Codex or Cursor. A winning short video goes in; its formula comes back rebuilt around your product on engines we run in production (the working manuals are public), with your own locked character if you want one, as a video file with no usage term or platform limit from us. When Riffkit has the source's music as its own track, the riff keeps that BGM by default: the music is part of why the video won, and the new video follows its beats. The track's rights stay with its owner, so check you're cleared to use it in your ads. Your TikTok ads agent can then upload and launch the video through this very MCP server. Agent runs the campaign, Riffkit makes the ammunition. That division of labor is, as of this year, how the whole stack was clearly designed to work.