douyin-ops-mcp
Related Servers
Alternatives to douyin-ops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables retrieval and management of social media data from Instagram, TikTok, YouTube, X, and Facebook through MCP tools, supporting extractions, search, discovery, batches, schedules, and saved results.71 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants and growth agents to search TikTok videos, extract spoken viral hooks and scripts, discover creator emails, mine buyer-intent comments, identify active brand sponsors, and scan breakout sounds through MCP tools.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to collect and localize content from WeChat, Douyin, Kuaishou, Xiaohongshu, and Bilibili, with 47 MCP tools for fetching articles, parsing media, and managing a unified local content library.1-
- FlicenseNot gradedqualityDmaintenanceProvides unified access to social media data across nine networks (Instagram, TikTok, YouTube, etc.) through a set of MCP tools for profiles, posts, search, and comments, backed by the SocialBridge API.-
- AlicenseBqualityBmaintenanceEnables scheduling and publishing social posts across 18 platforms from MCP clients, with media uploads, analytics, comment replies, and Google Business review management.731,614 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered LinkedIn automation, including content generation, profile and company data extraction, connection requests, and post scraping through MCP tools.-
TDQS
Scored across 29 tools
Several pairs have unclear boundaries: douyin_comments vs douyin_comments_list both read a work's comments, and douyin_local_check vs douyin_publish_preflight both validate local files (duration, resolution, audio, size) before publishing. douyin_notifications vs douyin_unread_count, douyin_parse vs douyin_breakdown (parse with optional transcription), and douyin_video_stats vs douyin_my_videos also overlap. Descriptions help somewhat, but an agent can easily pick the wrong twin.
All names are snake_case with a consistent douyin_ prefix, which is good. But the verb/noun ordering is mixed: publish_video / publish_images are verb_noun, while comment_publish and the queue_add/queue_list/queue_cancel family are noun_verb, and others are noun-only (trending, comments, breakdown, digg). Singluar/plural inconsistency between comments and comment_* adds to the confusion.
29 tools exceeds the comfortable 25-tool range, but the domain genuinely spans ingestion (parse/download), discovery (search/trending/profile), publishing (video/images/queue), analytics, comments, and login. Most tools earn their place; consolidating the duplicate pairs (comments/comments_list, local_check/preflight) would bring it to a healthy size.
Coverage is strong across the whole operational loop: parse/download, search/trending, login lifecycle, preflight + dryRun publishing, scheduling queue, analytics, and comment read/reply/publish. Gaps include no update/delete of published works and no follow/engagement actions beyond digg, but core workflows have no dead ends.