Skip to main content
Glama

Related Servers

Alternatives to douyin-ops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables scheduling and publishing social posts across 18 platforms from MCP clients, with media uploads, analytics, comment replies, and Google Business review management.
      73
      1,614 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 29 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues