Skip to main content
Glama
222wcnm

Bilibili Comments MCP

by 222wcnm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Bilibili Comments MCP

No user-submitted related servers found.

    Related Servers

    • Bilibili API MCP Server

      SMYB5431
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Bilibili (哔哩哔哩) through its API, supporting video search and recommendations, user search, dynamic feeds, video collections, and danmaku retrieval through natural language.
      5
      -

    • polylens-bilibili

      liu-xindi
      A
      license
      B
      quality
      B
      maintenance
      Enables reading public Bilibili video information — keyword search, UP profiles and uploads, video details and parts, comments and replies, danmaku, subtitles, and frame snapshots — through an MCP interface, with optional Bilibili login for authenticated features such as comments and subtitles.
      16
      96 PyPI
      3
      Apache 2.0

    • bili

      wjw-exe
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to search and open Bilibili videos, control a logical playback clock (play/pause/seek), read and post comments, like, coin, favorite, and fetch or export subtitle tracks through compact plain-text tool output. Write operations require a Bilibili login, which can be established by QR scan in an accompanying web console.
      MIT

    • bilinote-mcp

      caiqianzhang
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to access Bilibili video data and turn videos into notes, including search, video info, subtitles, chapters, audio download, ASR transcription, comments, uploader collections, and favorites.
      15
      41 PyPI
      2
      MIT
    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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one targets dynamic comments and the other targets video comments, with no overlap in functionality. The descriptions reinforce this by specifying different contexts (dynamic vs. video) while sharing similar features like pagination and nested replies.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_dynamic_comments and get_video_comments), using the same verb 'get' and similar noun structures. This makes the naming predictable and easy to understand across the tool set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a comments-focused domain, lacking operations like creating, updating, deleting, or searching comments. This minimal set may limit agent workflows, as it only supports retrieval without full CRUD coverage.

    Completeness2/5

    The tool set is severely incomplete for a comments domain, missing essential operations such as posting comments, replying to comments, or deleting comments. While retrieval is covered for dynamics and videos, there are significant gaps that will hinder agents from performing common comment-related tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources