Merge Unified's TikTok integration Merge Agent Handler's TikTok MCP server

Connect your AI Agents to TikTok in minutes

Merge lets you securely connect your agents to TikTok and thousands of tools instantly

Start building for free

Read docs

TikTok

Learn more about Merge Agent Handler

Available tools

get_creator_info

Get the authenticated creator's posting settings: available privacy levels, max video duration, and duet/stitch/comment defaults. Call before initvideopost. Requires video.publish scope.

init_video_post

Initialize a TikTok video post. For PULLFROMURL provide videourl; for FILEUPLOAD provide chunksize and totalchunkcount. Returns publishid (track with getpoststatus) and uploadurl for FILEUPLOAD. Requires video.publish scope.

init_photo_post

Initialize a TikTok photo carousel post with up to 35 photo URLs. Returns publishid to track with getpost_status. Requires video.publish scope.

get_post_status

Check the publishing status of a TikTok post by publishid. Status values: PROCESSINGDOWNLOAD, SENDTOUSERINBOX, PUBLISHCOMPLETE, FAILED. Requires video.publish scope.

get_user

Get the authenticated TikTok user's profile: display name, avatar, bio, follower/following counts, and verification status. Requires user.info.basic scope.

validate_credential

Validate TikTok Open Platform OAuth credentials by calling the user info endpoint.

list_videos

List the authenticated user's public TikTok videos, sorted by creation date descending. Use cursor from page_info to fetch the next page. Requires video.list scope.

get_videos

Retrieve specific TikTok videos by their IDs (up to 20 at a time). Use list_videos to browse and find video IDs. Requires video.list scope.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's TikTok MCP server

What is a TikTok MCP?

It's an MCP server that lets your agents access data and functionality from TikTok via tools. Your agents can invoke these tools to publish a video to a connected account, check the status of a pending post, pull engagement metrics for existing videos, review a creator's posting settings, and more.

TikTok offers an official MCP server built for its Ads platform, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the TikTok MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

Campaign performance alerts: an agent monitors ad group results throughout the day and posts to Slack when cost-per-result crosses a set threshold, so the media buyer can react before spend gets wasted

Budget pacing automation: triggered by a scheduled check, an agent compares actual spend against the daily budget for a campaign and pauses an ad group that's on track to overspend

Cross-channel ad reporting: an agent pulls TikTok ad performance alongside Meta and Google Ads data and assembles a single weekly spend and results summary for the growth team

Content performance summaries: an agent reviews recently published videos, ranks them by views and engagement, and sends a Monday recap to the content team so they know what to repeat

What are popular tools for TikTok's MCP server?

Here are some of the most commonly used tools:

list_videos: retrieves a paginated list of a creator's public videos. Useful for agents building a content library view or scanning for recent posts to summarize

get_videos: fetches details on up to 20 specific videos by ID, including engagement counts. Use this when an agent already has video IDs and needs performance data for a report

init_video_post: starts a video publish, either from a URL or a direct file upload. Call this when an agent needs to push new content live on a schedule or in response to an approval

init_photo_post: starts a photo carousel post of up to 35 images. Good for workflows that publish product or campaign photo sets instead of video

get_post_status: checks whether a publish job has completed, failed, or is still processing, using its publish ID. Helpful when an agent needs to confirm a post went live before notifying a stakeholder

get_creator_info: returns the authenticated creator's posting settings and privacy options. Useful for agents that need to confirm what posting permissions and defaults apply before initiating a publish

What makes Merge Agent Handler's TikTok MCP server better than alternative TikTok MCP servers?

There are several reasons to use Merge Agent Handler's TikTok MCP server over building or maintaining your own:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For TikTok, this means you can prevent ad spend and budget figures, audience targeting parameters, and creator account details from being exposed even when the agent has broad read access

Managed authentication and credentials: Merge stores and refreshes TikTok credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or manage token rotation manually

Real-time observability and audit trail: Every tool call made against TikTok is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent read or wrote without instrumenting anything yourself

Tool Packs and controlled access: Tool Packs let you bundle specific TikTok tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's TikTok MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose TikTok and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying TikTok data directly. The first time you use a TikTok tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's TikTok MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge to connect their AI tools to TikTok?

Yes, Merge for Workforce lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to TikTok without bypassing IT governance.

IT can provision access by role or group via SCIM. A growth marketer, for example, gets TikTok access to review campaign spend, Google Ads access to compare cross-channel performance, and Slack access to share weekly results with the team; while a content strategist gets TikTok access to publish and review video performance, Asana access to track content calendar tasks, and Google Drive access to pull approved creative assets.

Every tool call an employee's AI makes to TikTok is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.