Skip to main content
Glama
deenesjakoruzh
trendsmcp-ai

tiktok-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tiktok-trends-mcp

TikTok Trends MCP Works with Claude Works with Cursor

AI 어시스턴트를 위한 TikTok 트렌드 데이터 TikTok 트렌드가 대중화되기 전에 포착하세요. 해시태그 볼륨 성장, 바이럴 급증, 플랫폼별 수요 신호를 추적하세요. AI에서 일반 언어로 모두 접근 가능합니다.

전체 문서 및 라이브 데모: https://trendsmcp.ai/tiktok-trends

**Trends MCP**의 일부 - 12개 이상의 소스에서 실시간 트렌드 데이터를 제공하는 MCP 서버입니다. 메인 저장소: https://github.com/trendsmcp/trends-mcp

2단계로 시작하기

1단계: **trendsmcp.ai**에서 무료 API 키 받기 하루 100회 요청 가능, 신용카드 불필요.

2단계: AI 클라이언트에 추가 (YOUR_API_KEY를 교체):

+ Cursor에 추가 (원클릭)

Cursor / Windsurf / Cline   (~/.cursor/mcp.json 또는 동등 파일)

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

VS Code / GitHub Copilot   (.vscode/mcp.json)

{
  "servers": {
    "trends-mcp": {
      "type": "http",
      "url": "https://api.trendsmcp.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Claude Desktop   (claude_desktop_config.json) 사용자 → 설정 → 개발자 → 구성 편집 — mcpServers 내부에 추가

{
  "mcpServers": {
    "trends-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.trendsmcp.ai/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude.ai (브라우저)   설정 → 커넥터 → 사용자 정의 커넥터 추가:

https://api.trendsmcp.ai/mcp

Related MCP server: tiktok-trends-mcp

예시 질문

연결 후 AI에게 물어보세요:

get_trends(keyword='booktok', source='tiktok', data_mode='weekly')

사용 가능한 도구

도구

기능 설명

get_trends

이 소스에서 키워드의 시계열 데이터 조회

get_growth

1주, 1개월, 3개월, 6개월, 1년 기간별 성장률

get_top_trends

이 소스에서 현재 인기 있는 트렌드 조회

get_ranked_trends

볼륨 기준 상위 주제 순위 조회

FAQ

Trends MCP는 어떤 TikTok 데이터를 제공하나요?

TikTok 해시태그 트렌드 볼륨 - 정규화된 관심도, 성장률, 과거 시계열 데이터입니다. 이는 해시태그가 플랫폼에서 얼마나 자주 나타나고 성장하는지를 반영합니다.

TikTok 트렌드를 얼마나 빨리 감지할 수 있나요?

Trends MCP는 주간 및 일간 데이터를 제공합니다. 일간 데이터(최근 30일)를 통해 해시태그가 주류 포화 상태에 도달하기 전 초기 성장 급증을 포착할 수 있습니다.

TikTok 트렌드를 Google 검색과 비교할 수 있나요?

네. 한 번의 호출로 두 소스를 모두 쿼리할 수 있습니다. TikTok은 동일한 주제가 Google 검색에서 상승하기 2-4주 전에 급증을 보이는 경우가 많아, 교차 플랫폼 비교가 선행 지표 전략이 됩니다.

브랜드 모니터링에 TikTok 데이터를 사용할 수 있나요?

네. 브랜드명이나 제품 해시태그를 시간에 따라 추적하여 경쟁사 대비 TikTok에서의 존재감 성장을 측정할 수 있습니다.

TikTok 해시태그는 대소문자를 구분하나요?

아니요. 쿼리는 조회 전에 정규화됩니다. 'booktok', 'BookTok', '#booktok' 모두 동일한 신호를 반환합니다.

모든 데이터 소스

Trends MCP는 하나의 연결로 12개 이상의 소스를 지원합니다: Google 검색, YouTube, TikTok, Reddit, Amazon, Wikipedia, 뉴스 감성, 웹 트래픽, 앱 다운로드, Steam, npm 등.

전체 목록: https://trendsmcp.ai/data-sources

Python 클라이언트로도 사용 가능

동일한 API 키가 Python에서 직접 작동합니다. MCP 호스트가 필요 없습니다.

pip install tiktok-trends-mcp
import os
from tiktok_trends_mcp import TrendsMcpClient, SOURCE

client = TrendsMcpClient(api_key=os.environ["TRENDSMCP_API_KEY"])

series  = client.get_trends(source=SOURCE, keyword="your keyword")
growth  = client.get_growth(source=SOURCE, keyword="your keyword", percent_growth=["1M", "3M", "12M"])
top     = client.get_top_trends(type="Tiktok", limit=10)

전체 Python 문서: trendsmcp.ai/docs

라이선스

MIT © Trends MCP

Available Tools

3 tools
get_growthA
Read-onlyIdempotent
Inspect

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Prefer this over get_time_series for growth questions. app downloads and app rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesOne source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID.
percent_growthNoGrowth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y', '60M', '5Y', 'MTD', 'QTD', 'YTD'. Every preset is a two-date comparison.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description adds useful behavioral context: values are on a 0-100 scale with absolute volume when available, and the agent should tell the user their plan limit is reached on rate limiting or quota exhaustion. These details are not present in the structured fields and do not contradict the 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 compact and every sentence earns its place: core operation, output scale, sibling preference, app-source caveat, and rate-limit handling. It front-loads the primary purpose and avoids redundant phrasing.

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

Completeness5/5

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

With a detailed input schema, an output schema, and safety annotations, the description fills the remaining gaps: tool selection, output scale, source disambiguation, and error behavior. It is complete enough for an agent to invoke the tool correctly without further inference.

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 input schema already documents all parameters thoroughly, including valid sources, keyword formatting rules per source, and every preset growth window. The description references preset windows and Android bundle IDs but does not add meaning beyond the schema, so a baseline of 3 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 opens with a specific action and resource: 'Point-to-point growth for a keyword on one or more sources.' It also names sibling tools to disambiguate itself, stating it is preferred over get_time_series for growth questions and clarifying that app sources are not the live boards on get_top_trends.

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

Usage Guidelines5/5

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

It gives an explicit selection rule: 'Prefer this over get_time_series for growth questions.' It also warns against confusing app downloads/app rankings with get_top_trends live boards, and specifies how to handle rate limits or quota exhaustion. This gives the agent clear when-to-use and when-not-to-use guidance.

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

get_time_seriesA
Read-onlyIdempotent
Inspect

Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesExactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'tesla'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint. The description adds behavioral context beyond those hints: the 0-100 value range, volume availability, and rate-limit/quota handling instructions. This provides useful operational detail that annotations do not convey, though the core safety profile is already covered by hints.

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?

Three sentences, each earning its place: purpose and scope, usage routing, and error handling. Front-loaded with the core purpose; no repetition or fluff. The alternative tool routing is included efficiently.

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

Completeness5/5

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

Given a two-parameter tool with a full output schema, the description covers purpose, usage scenarios, alternatives, and error handling. An agent has all necessary information to decide when to call it and what to expect, with no critical gaps.

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?

Schema description coverage is 100% and both parameters have detailed, source-specific descriptions (e.g., keyword format per source, valid source list). The tool description adds no additional parameter meaning beyond restating 'one keyword and one source', so the baseline for full schema coverage applies.

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 explicitly states it returns 'Full historical series for one keyword and one source' with a value range and volume detail. It distinguishes itself from siblings get_top_trends and get_growth by stating what it is not for (live trending, growth questions), making the tool's purpose unambiguous.

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

Usage Guidelines5/5

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

Directly states when to use it: 'Use for charting or custom math' and when not to: 'Not for live trending (use get_top_trends)' and 'For most growth questions, use get_growth'. Also provides explicit handling for rate-limited or quota-exhausted requests, which is actionable guidance.

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.

  1. 3 tool updatesv0.1.0
    • First observedget_growth
    • First observedget_time_series
    • First observedget_top_trends
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool addresses a distinct retrieval pattern: get_growth handles window-over-window comparisons for keyword sources, get_time_series provides full historical data for charting, and get_top_trends targets current live boards without a keyword. The descriptions explicitly cross-reference each other and state when one is preferred, so an agent should be able to select correctly.

Naming Consistency5/5

All three tool names follow the same get_ + noun pattern using snake_case, making the collection predictable. There are no mixed conventions or vague verbs.

Tool Count5/5

Three tools is well-scoped for a trends data server: one for growth comparisons, one for full history, and one for live top lists. Each tool provides a distinct high-level capability without redundancy or bloat.

Completeness4/5

The read-only trend surface is broadly covered: live boards, point-to-point growth, and historical series cover the main ways trends data would be requested. A minor gap is that there is no explicit discovery tool for available sources/categories, though the descriptions document them sufficiently for most workflows.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers