Which integrations are available for this server?

Provides tools for managing and reporting on TikTok advertising campaigns, ad groups, ads, and performance reports via the TikTok Business API.

How do I use tiktok-ads-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@tiktok-ads-mcp list my active campaigns" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

tiktok-ads-mcp

by ysntony

Overview Schema Source Related Servers Discussions Admin

Python

Remote

TikTok Ads MCP

A comprehensive Model Context Protocol (MCP) server for interacting with the TikTok Business API. This package provides a complete interface to access TikTok advertising campaigns, ad groups, ads, and generate detailed performance reports.

Features

Read-Only TikTok Business API Integration: Access all major TikTok advertising endpoints for data retrieval
6 Comprehensive Tools: Business centers, ad accounts, campaigns, ad groups, ads, and reports
Advanced Filtering: Powerful filtering options for all data retrieval operations
Multi-Advertiser Support: Handle multiple advertiser accounts in a single request
Flexible Reporting: Generate detailed performance reports with custom dimensions and metrics
Real-time Data: Access live advertising data and performance metrics
Error Handling: Comprehensive error handling and validation
Modular Architecture: Clean, maintainable code structure
Safe Operations: All tools are read-only and will not modify your campaigns or ad data

Related MCP server: Reddit Ads MCP Server

Available Tools

get_business_centers - Retrieve business centers accessible by your access token
get_authorized_ad_accounts - Get all authorized advertiser accounts
get_campaigns - Retrieve campaigns with comprehensive filtering options
get_ad_groups - Get ad groups with advanced filtering and targeting options
get_ads - Retrieve ads with detailed creative and performance data
get_reports - Generate comprehensive performance reports and analytics

Prerequisites

Python 3.10 or higher
TikTok Business API access
Valid API credentials (app ID, secret, access token)

Quick Start

Installation

Download the TikTok Ads MCP
- Click the green "Code" button at the top of the GitHub page
- Select "Download ZIP"
- Unzip the downloaded file to a location you can easily find (like your Documents folder)

Alternatively, if you're familiar with Git:

git clone https://github.com/ysntony/tiktok-ads-mcp.git

Install Dependencies

cd tiktok-ads-mcp
pip install -e .
# or with uv
uv pip install -e .

Configuration

Set up environment variables in your MCP client configuration:

{
  "mcpServers": {
    "tiktok-ads": {
      "command": "python",
      "args": ["-m", "tiktok_ads_mcp"],
      "env": {
        "TIKTOK_APP_ID": "your_app_id",
        "TIKTOK_SECRET": "your_secret",
        "TIKTOK_ACCESS_TOKEN": "your_access_token"
      }
    }
  }
}

Required credentials:
- TIKTOK_APP_ID: Your TikTok app ID
- TIKTOK_SECRET: Your TikTok app secret
- TIKTOK_ACCESS_TOKEN: Your access token
How to get these credentials:
1. Go to the TikTok for Business Developers portal and log in.
2. Click "My Apps" and create a new app.
3. Select "Marketing API" as the service type.
4. In the app settings, enable permissions related to Reading and Reporting (e.g., Ads Management, Reporting).
5. Once approved, you will find your App ID and Secret in the app details.
6. Generate an Access Token using the "TikTok Marketing API Inspector" or via the OAuth flow documented in the portal.

Usage

Once configured, you can use the MCP tools through your MCP client (like Cursor, Claude Desktop, etc.):

Get business centers and advertiser accounts to discover available accounts
Retrieve campaigns with filtering by status, objective, or date range
Access ad groups with advanced targeting and optimization settings
View ads with detailed creative and performance data
Generate reports with custom dimensions, metrics, and time ranges
Access real-time advertising data and performance metrics

API Coverage

This MCP server provides read-only access to the TikTok Business API:

Business Management

Business center retrieval and access
Advertiser account information and permissions

Campaign Management

Campaign retrieval and filtering
Campaign status and performance monitoring
Campaign budget and objective information

Ad Group Management

Ad group retrieval and filtering
Advanced targeting and optimization settings
Performance monitoring and analysis

Ad Management

Ad retrieval and filtering
Creative asset information
Performance tracking and analysis

Reporting & Analytics

Basic performance reports
Audience insights reports
Playable ads reports
DSA (Dynamic Search Ads) reports
Business Center reports
GMV max ads reports

Key Features

Advanced Filtering

All tools support comprehensive filtering options:

Status-based filtering (active, paused, deleted)
Time-based filtering (creation date, modification date)
Performance-based filtering (budget, optimization goals)
Creative filtering (ad formats, material types)

Modern Implementation

This package uses the FastMCP framework for optimal performance and developer experience:

Automatic Schema Generation: From Python type hints
Simplified Tool Registration: Using @app.tool() decorators
Built-in Error Handling: Consistent error responses
Type Safety: Full parameter validation from type hints

Multi-Advertiser Support

Handle multiple advertiser accounts in single requests
Cross-advertiser reporting and analytics
Unified data access across accounts

Flexible Reporting

Custom dimensions and metrics
Multiple report types and data levels
Time-based and lifetime metrics
Aggregated and detailed views

Error Handling

Comprehensive parameter validation
Detailed error messages and suggestions
Graceful handling of API limitations
Rate limiting and retry logic

Documentation

MCP_USAGE.md: Comprehensive usage guide with examples
TikTok Business API: Official API documentation
Project Wiki: Additional resources and guides

Contributing

Fork the repository
Create a feature branch
Implement your changes
Add tests and documentation
Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For issues and questions:

Check the MCP_USAGE.md documentation
Review the TikTok Business API documentation
Open an issue on the GitHub repository
Contact the development team

Changelog

v0.1.4 (Current)

Retry Logic Fix: Fixed retry decorator being defeated by inner exception handling — retries now actually fire on rate limits and transient errors
Pagination Fix: page and page_size params now properly passed through to get_ad_groups and get_ads API calls
Security: Access token redacted from debug log output
Dependencies: Removed unused requests and pandas, bumped mcp to >=1.27.0, added httpx and tenacity to requirements.txt
Code Quality: Modernized type annotations to Python 3.10+ style, removed dead code and redundant error checks, fixed mutable default dict mutation in filter handling
Python Compatibility: Lowered minimum Python version to 3.10

v0.1.3

Async Support: Complete refactor to use async/await with httpx for improved performance
Retry Logic: Added automatic retries for rate limits and server errors using tenacity
Error Handling: Simplified and standardized error handling with decorators
Dependencies: Switched from requests to httpx

v0.1.2

FastMCP Implementation: Modern MCP server using official FastMCP framework
70% Code Reduction: Compared to traditional MCP implementations
Automatic Schema Generation: From Python type hints
Simplified Tool Registration: Using @app.tool() decorators
Enhanced Error Handling: Built-in error handling with consistent responses
Type Safety: Full parameter validation from type hints
Future-Proof: Part of the official MCP SDK

v0.1.1

Complete implementation of all 6 tools
Advanced filtering and reporting capabilities
Multi-advertiser support
Comprehensive error handling
Modular tools architecture
Complete documentation and usage guides

v0.1.0

Initial release with basic MCP server structure
Core API client implementation
Basic authentication and configuration

Available Tools

6 tools

get_ad_groups_toolC

Get ad groups for a specific advertiser with optional filtering

ParametersJSON Schema

Name	Required	Description	Default
`advertiser_id`	Yes
`campaign_id`	No
`filters`	No
`page`	No
`page_size`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention any traits such as safety (read-only nature), pagination behavior, or authentication requirements, leaving the agent uninformed about side effects or access needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the tool's purpose. It is efficient but could include more detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters with no schema descriptions) and the existence of an output schema, the description should provide more context on parameter usage and behavioral details. It lacks completeness for reliable agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It only mentions 'optional filtering' without explaining the filters, campaign_id, pagination parameters, or their expected formats. This is insufficient for an agent to use the tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Get) and resource (ad groups) with scope (specific advertiser) and optional filtering. However, it does not explicitly distinguish this tool from sibling tools like get_campaigns_tool or get_ads_tool, which would elevate it to a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The agent must infer usage from context alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_ads_toolC

Get ads for a specific advertiser with optional filtering

ParametersJSON Schema

Name	Required	Description	Default
`advertiser_id`	Yes
`adgroup_id`	No
`filters`	No
`page`	No
`page_size`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description bears full responsibility for behavioral traits. It only states 'Get ads', implying a read operation, but fails to disclose pagination behavior, rate limits, authentication needs, or any side effects. The output schema exists but is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is concise but at the expense of completeness, which is acceptable for this dimension since conciseness is valued.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, 0% schema coverage, no annotations, and an output schema, the description is insufficient. It omits details on pagination, filtering structure, and the optional adgroup_id parameter, leaving the agent with incomplete context for tool usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description only vaguely hints at advertiser_id and filters without explaining any of the 5 parameters. It adds no meaningful semantics beyond the schema's own parameter names and types, leaving adgroup_id, page, and page_size unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves ads for a specific advertiser with optional filtering. It distinguishes from sibling tools like get_ad_groups_tool and get_campaigns_tool by specifying the resource and the key identifier (advertiser).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives. It lacks explicit context for appropriate usage or exclusions, despite the presence of sibling tools like get_authorized_ad_accounts_tool and get_reports_tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_authorized_ad_accounts_toolA

Get all authorized ad accounts accessible by the current access token

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Given no annotations, the description carries full burden. It accurately describes the tool as a read-only retrieval operation (no destructive behavior). It is transparent about the scope ('accessible by the current access token'). For a simple read tool, this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that effectively communicates the purpose. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for this simple tool. An output schema exists (though not shown) to detail return values. However, missing context about potential pagination or limitations if the account list is large. Still, overall complete given the lack of parameters and straightforward behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so schema coverage is 100%. The description adds no parameter information because none is needed. Baseline of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves all authorized ad accounts accessible by the current access token. It uses a specific verb ('Get') and resource ('authorized ad accounts'), and distinguishes itself from sibling tools that operate on campaigns, ads, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool is the starting point for accessing ad accounts, but does not explicitly state when to use it versus alternatives like get_campaigns or get_ads. No when-not or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_business_centers_toolC

Get business centers accessible by the current access token

ParametersJSON Schema

Name	Required	Description	Default
`bc_id`	No
`page`	No
`page_size`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description implies read-only access but lacks details on pagination, rate limits, or behavior when no centers are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but too minimal, missing parameter details and usage context. It is front-loaded but under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description partially covers return values, but it omits pagination behavior and filtering semantics, making it incomplete for a 3-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and description provides no explanation of page, bc_id, or page_size parameters, leaving the agent to infer their purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves business centers accessible by the current token. It distinguishes from sibling tools focused on ads and reports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no exclusions or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_campaigns_toolB

Get campaigns for a specific advertiser with optional filtering

ParametersJSON Schema

Name	Required	Description	Default
`advertiser_id`	Yes
`filters`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It does not mention pagination, rate limits, permissions, data freshness, or what happens when no campaigns match. The description is too sparse for a tool without annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no unnecessary words. It front-loads the core action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and the presence of an output schema, the description is too minimal. It omits details about pagination, error handling, and filter format that an AI agent might need for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning by implying that 'advertiser_id' is the main identifier and that 'filters' are optional. However, it does not explain the structure of filters (the schema shows an object but no description). With 0% schema coverage, the description compensates partially but could be more explicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get'), resource ('campaigns'), and the required context ('for a specific advertiser'). It also mentions optional filtering, which distinguishes it from sibling tools like get_ad_groups_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what the tool does without any usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_reports_toolC

Get performance reports and analytics with comprehensive filtering and grouping options

ParametersJSON Schema

Name	Required	Default
`advertiser_id`	No
`advertiser_ids`	No
`bc_id`	No
`report_type`	No	BASIC
`data_level`	No	AUCTION_CAMPAIGN
`dimensions`	No
`metrics`	No
`start_date`	No
`end_date`	No
`filters`	No
`page`	No
`page_size`	No
`service_type`	No	AUCTION
`query_lifetime`	No
`enable_total_metrics`	No
`multi_adv_report_in_utc_time`	No
`order_field`	No
`order_type`	No	DESC

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It implies a read operation but doesn't disclose side effects, permissions, rate limits, or return format beyond 'reports and analytics'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it lacks necessary details. It is front-loaded but not efficiently structured to convey essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 18 parameters, no annotations, and an output schema present but not described, the description is severely incomplete. It fails to provide sufficient context for an agent to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only vaguely mentions 'filtering and grouping options' without explaining any of the 18 parameters (e.g., filters, dimensions, metrics).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets performance reports and analytics with filtering and grouping, but it doesn't differentiate from sibling tools like get_ads_range_report_tool or get_gmvmax_reports_tool that may have similar purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no exclusions, and no context about prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

6 tool updatesv0.1.4Jun 11, 2026
- First observedget_ad_groups_tool
- First observedget_ads_tool
- First observedget_authorized_ad_accounts_tool
- First observedget_business_centers_tool
- First observedget_campaigns_tool
- First observedget_reports_tool

Deploy Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Scored 2026-06-12 13:31 across 6 tools

Disambiguation5/5

Each tool retrieves a distinct entity (ad groups, ads, ad accounts, business centers, campaigns, reports) with no overlapping purposes, making it clear which tool to use for a given resource.

Naming Consistency5/5

All tools follow the consistent pattern 'get_<resource>_tool' with snake_case, making the naming predictable and easy to infer.

Tool Count5/5

With 6 tools covering the main read operations for TikTok Ads, the number is well-scoped for a focused MCP server, not too many or too few.

Completeness4/5

The server covers all major read entities (ad accounts, business centers, campaigns, ad groups, ads, reports) but lacks create/update/delete operations, which is acceptable if intended as read-only; minor gap for read-only completeness.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

reporting-ninja
com.reportingninja
Read-only access to your Reporting Ninja marketing and analytics data across 20+ ad platforms.
Marketing Research & Data
2
adwhizOAuth
com.7275
Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.
Marketing AI & Machine Learning
1
Meta Ads (Facebook & Instagram)B
io.github.mcp-dir
Read and manage Meta Ads campaigns, ad sets, ads, audiences, pages and Business Manager. You provide
Marketing Social Media
441
AdsAgent — TikTok Ads MCPOAuth
md.adsagent
Hosted TikTok ads MCP with OAuth, bounded reads, and prepare/confirm writes.
Marketing Social Media
1

Related MCP Servers

TikTok Ads MCP
Marketing Social Media
Buer2333
A
license
B
quality
B
maintenance
A read-only MCP server that provides comprehensive access to the TikTok Business API for retrieving advertising data, including campaigns, ad groups, ads, and performance reports.
Updated 17 days ago (2026-08-27 07:47 UTC)
24
MIT
Reddit Ads MCP Server
Marketing Social Media
sbmeaper
F
license
Not graded
quality
D
maintenance
Read-only access to Reddit Ads API v3 for listing ad accounts, campaigns, ad groups, ads, and generating performance reports with OAuth2 authentication.
Updated 8 months ago (2026-01-11 19:27 UTC)
-
Meta Ads MCP Server
Marketing Social Media
isaganiesteron
F
license
Not graded
quality
D
maintenance
Provides read-only access to Meta Ads API, enabling campaign management, creative analysis, targeting research, and performance analytics via 39 tools.
Updated 3 months ago (2026-06-25 07:54 UTC)
-
Ads Analytics MCP
Marketing Research & Data
Pauesome
A
license
Not graded
quality
C
maintenance
Provides read access to campaign performance data from Google Ads, Meta Ads, and TikTok Ads via live API calls, enabling AI assistants to analyze and audit advertising campaigns.
Updated 3 months ago (2026-06-28 09:39 UTC)
1
MIT