I
IvanBBaev/tiktok-mcp
Unofficial TikTok MCP server — policy-governed tools over the official Display and Content Posting APIs, with…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"ivanbbaev-tiktok-mcp": {
"command": "npx",
"args": ["tiktok-mcp-ai"]
}
}
}Parsed from the README we fetched on 2026-11-07; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"ivanbbaev-tiktok-mcp": {
"command": "npx",
"args": ["tiktok-mcp-ai"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio ivanbbaev-tiktok-mcp -- npx tiktok-mcp-ai
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · IvanBBaev/tiktok-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-08 · last seen 2026-11-14 · seen 7× · listed by 1 sources
- Score
- score 103 · 1 ★ · 1 sources · repo
- Install
npx tiktok-mcp-ai
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx tiktok-mcp-ai. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
IvanBBaev/tiktok-mcp；first catalogued 2026-11-08；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# tiktok-mcp-ai — Unofficial TikTok MCP Server
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
📖 Documentation site →
An unofficial MCP (Model Context Protocol)
server for TikTok — a safe, policy-governed tool surface over the official
TikTok for Developers APIs: the Display API
(read a creator's profile and videos) and the Content Posting API (publish
videos and photo carousels). It adds OAuth 2.0 (PKCE) user authorization,
plan-then-execute write safety, an append-only publish journal, multi-account
profiles, and token-efficient results — so a model can work with TikTok without
knowing any of the platform's sharp edges (24-hour tokens, cursor pagination,
chunked uploads, per-token rate limits, the app-audit gate, and an error
envelope that hides failures inside HTTP 200 responses).
> Unofficial project. This is an independent, community-built MCP server. It
> is not affiliated with, endorsed by, or sponsored by TikTok or ByteDance
> Ltd. "TikTok" is a trademark of its owner, used here only nominatively to
> identify the service this server connects to. See Trademark.
Contents: Quick demo · Features ·
Requirements · Setup ·
Configure credentials · Run / debug ·
Develop · Tools · Security notes ·
Uninstall · Project documentation ·
Support · Trademark
_Built and maintained in my own time — if it helps, a
GitHub Sponsors tip keeps it going.
Full Support options are near the end._
## Quick demo
The signature move is safe publishing: a write tool never mutates on the
first call. Point your MCP client at a TikTok app (Setup), authorize
once (npx tiktok-mcp-ai login), and ask:
1. "Post this clip — but show me exactly what will happen first." The model
calls tiktok_post_video without a plan_id. Nothing is posted: the result
is a full, human-readable preview — the resolved creator identity, the
privacy level, every flag, the chunk plan for the upload, the exact upstream
request that would be sent — plus a single-use plan_id valid for 10 minutes:
jsonc
// tiktok_post_video — preview (no plan_id ⇒ nothing is posted)
"source": "file",
"file_path": "clips/launch-teaser.mp4",
"post_info": {
"title": "Launch day! #buildinpublic",
"privacy_level": "PUBLIC_TO_EVERYONE",
},
2. "Looks right — do it." The model calls the same tool again with the
plan_id from the preview. The payload is re-resolved through the identical
code path, its SHA-256 digest is compared against the plan, the plan is consumed
atomically, and only then is the upload dispatched — so a retry can never
double-post, and nothing but the previewed payload can ever run:
jsonc
// tiktok_post_video — execute (the plan_id selects execution)
"source": "file",
"file_path": "clips/launch-teaser.mp4",
"post_info": {
"title": "Launch day! #buildinpublic",
"privacy_level": "PUBLIC_TO_EVERYONE",
},
"plan_id": "plan_9f2c7b1e4a6d0c83f5b2e19a7d4c6f80",
3. "Did anything actually post?" Every attempt — intent before the request,
outcome after — is written to a local append-only journal. Read it back with a
tool, no matter which client made the post:
bash
npx tiktok-mcp-ai doctor # among other checks: reconciles the publish journal
All read tools are safe to call anytime; the four write tools are the only ones
gated by plan-then-execute, and they return the publish_id immediately so the
An unofficial MCP (Model Context Protocol)
server for TikTok — a safe, policy-governed tool surface over the official
TikTok for Developers APIs: the Display API
(read a creator's profile and videos) and the Content Posting API (publish
videos and photo carousels). It adds OAuth 2.0 (PKCE) user authorization,
plan-then-execute write safety, an append-only publish journal, multi-account
profiles, and token-efficient results — so a model can work with TikTok without
knowing any of the platform's sharp edges (24-hour tokens, cursor pagination,
chunked uploads, per-token rate limits, the app-audit gate, and an error
envelope that hides failures inside HTTP 200 responses).
> Unofficial project. This is an independent, community-built MCP server. It
> is not affiliated with, endorsed by, or sponsored by TikTok or ByteDance
> Ltd. "TikTok" is a trademark of its owner, used here only nominatively to
> identify the service this server connects to. See Trademark.
Contents: Quick demo · Features ·
Requirements · Setup ·
Configure credentials · Run / debug ·
Develop · Tools · Security notes ·
Uninstall · Project documentation ·
Support · Trademark
_Built and maintained in my own time — if it helps, a
GitHub Sponsors tip keeps it going.
Full Support options are near the end._
## Quick demo
The signature move is safe publishing: a write tool never mutates on the
first call. Point your MCP client at a TikTok app (Setup), authorize
once (npx tiktok-mcp-ai login), and ask:
1. "Post this clip — but show me exactly what will happen first." The model
calls tiktok_post_video without a plan_id. Nothing is posted: the result
is a full, human-readable preview — the resolved creator identity, the
privacy level, every flag, the chunk plan for the upload, the exact upstream
request that would be sent — plus a single-use plan_id valid for 10 minutes:
jsonc
// tiktok_post_video — preview (no plan_id ⇒ nothing is posted)
"source": "file",
"file_path": "clips/launch-teaser.mp4",
"post_info": {
"title": "Launch day! #buildinpublic",
"privacy_level": "PUBLIC_TO_EVERYONE",
},
2. "Looks right — do it." The model calls the same tool again with the
plan_id from the preview. The payload is re-resolved through the identical
code path, its SHA-256 digest is compared against the plan, the plan is consumed
atomically, and only then is the upload dispatched — so a retry can never
double-post, and nothing but the previewed payload can ever run:
jsonc
// tiktok_post_video — execute (the plan_id selects execution)
"source": "file",
"file_path": "clips/launch-teaser.mp4",
"post_info": {
"title": "Launch day! #buildinpublic",
"privacy_level": "PUBLIC_TO_EVERYONE",
},
"plan_id": "plan_9f2c7b1e4a6d0c83f5b2e19a7d4c6f80",
3. "Did anything actually post?" Every attempt — intent before the request,
outcome after — is written to a local append-only journal. Read it back with a
tool, no matter which client made the post:
bash
npx tiktok-mcp-ai doctor # among other checks: reconciles the publish journal
All read tools are safe to call anytime; the four write tools are the only ones
gated by plan-then-execute, and they return the publish_id immediately so the
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/ivanbbaev-tiktok-mcp/)
- Source
- github · https://github.com/IvanBBaev/tiktok-mcp
- Browse by field
- Open source
- Traction
- 1 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.