tikhub-mcp
Skill7 starsChanged 5 months agoMITView on GitHub
Connect to and orchestrate TikHub's official hosted MCP server (mcp.tikhub.io). Use when the user wants Claude to call TikHub directly as tools, asks to enable more TikHub platforms, or hits MCP connection/auth issues. This plugin does NOT build its own MCP — it bridges TikHub's hosted MCP via npx mcp-remote.
- Reads credentials
- Installs packages
In this repository18 other files it gives its agents.
- bulk-data-exportSkill
- comments-analysisSkill
- competitor-analysisSkill
- creator-analyticsSkill
- douyinSkill
- hashtag-researchSkill
- instagramSkill
- social-listeningSkill
- social-media-downloaderSkill
- tikhub-endpoint-discoverySkill
- tikhub-onboardingSkill
- tikhub-python-sdkSkill
- tikhub-rest-apiSkill
- tiktokSkill
- trend-researchSkill
- twitter-threadsSkill
- xiaohongshuSkill
- youtubeSkill
The file
Files
TikHub — Hosted MCP
TikHub runs an official hosted MCP: 16 platform-based servers exposing 900+ tools at
https://mcp.tikhub.io/{platform}/mcp. This plugin's .mcp.json already wires the Core-6
platforms. This skill covers adding platforms, the self-host fallback, and troubleshooting.
Setup gate
[ -z "${TIKHUB_API_KEY:-}" ] && echo "Set TIKHUB_API_KEY first (see tikhub-onboarding)."
command -v npx >/dev/null 2>&1 || echo "npx (Node.js) not found — the hosted MCP path needs it. Use REST/SDK or self-host instead."How it's wired
The plugin ships .mcp.json with one entry per Core-6 platform, each bridging the hosted
endpoint through mcp-remote:
{
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.tikhub.io/tiktok/mcp",
"--header", "Authorization: Bearer ${TIKHUB_API_KEY}"]
}${TIKHUB_API_KEY} is expanded from the environment. After enabling the plugin run
/reload-plugins; the tikhub-* tools then appear to Claude.
Add more platforms
Available slugs and approximate tool counts:
| Slug | Tools | Slug | Tools |
tiktok | 204 | zhihu | 32 |
douyin | 247 | linkedin | 25 |
instagram | 56 | reddit | 24 |
xiaohongshu | 50 | youtube | 21 |
weibo | 64 | wechat | 19 |
bilibili | 38 | twitter | 13 |
kuaishou | 33 | threads | 11 |
others (Lemon8/PiPiXia/Xigua/Toutiao/Sora2) | 64 | tikhub (account/downloader/health) | 23 |
To enable one, add another mcpServers entry to .mcp.json with the slug swapped into the URL,
then /reload-plugins. Keep the enabled set lean — each platform adds many tools to context.
Self-host fallback (no Node / air-gapped)
pip install tikhub-mcp
export TIKHUB_API_KEY=your_key
tikhub-mcp --platform tiktok --transport stdio # single platform for Claude
tikhub-mcp --transport http --port 8000 # all platforms at http://localhost:8000/{platform}/mcpPoint .mcp.json at the local command instead of mcp-remote. Source: ~/PycharmProjects/TikHub_MCP.
Troubleshooting
- 401 / unauthorized →
TIKHUB_API_KEYmissing/invalid, or out of credits (check user.tikhub.io). npx: command not found→ install Node.js, or use the self-host / REST paths.- Tools don't appear → run
/reload-plugins; confirm.mcp.jsonis valid JSON. - Too many tools / context bloat → enable fewer platforms.
Red flags
- Trying to build or vendor an MCP server — don't; use the hosted one.
- Enabling all 16 platforms by default — bloats the tool surface.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

