Tiktok Ads Mcp Server

Created By
AdsMCP9 months ago
TikTok Ads MCP Server – Model Context Protocol Server for TikTok Ads Marketing API Integration
Overview

what is TikTok Ads MCP Server?

TikTok Ads MCP Server is a Model Context Protocol server designed for integrating with the TikTok Ads Marketing API, enabling AI assistants to manage advertising campaigns effectively.

how to use TikTok Ads MCP Server?

To use the server, clone the repository, set up the environment variables with your TikTok API credentials, and run the server using Python. Ensure you have a TikTok For Business account with API access.

key features of TikTok Ads MCP Server?

  • Campaign Management: Create, read, and update campaigns and ad groups.
  • Performance Analytics: Retrieve detailed performance metrics and insights.
  • Audience Management: Handle custom audiences and targeting options.
  • Creative Management: Upload and manage ad creatives.
  • Reporting: Generate and download custom performance reports.

use cases of TikTok Ads MCP Server?

  1. Managing TikTok advertising campaigns through AI assistants.
  2. Analyzing campaign performance metrics for optimization.
  3. Automating audience targeting and ad creative management.

FAQ from TikTok Ads MCP Server?

  • What are the prerequisites for using the server?

You need Python 3.10+, a TikTok For Business account with API access, and a registered TikTok Ads Developer account.

  • How do I authenticate with the TikTok Ads API?

You need to implement the OAuth 2.0 flow to obtain access tokens and manage user authorization.

  • Is there a limit on API requests?

Yes, the TikTok Ads API has rate limits, including 1000 requests per hour per app.

Project Info
Created At
9 months ago
Updated At
8 months ago
Author Name
AdsMCP
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago