Bilibili Comments Mcp

Created By
222wcnma year ago
B 站视频评论获取工具.
Overview

What is Bilibili Comments MCP?

Bilibili Comments MCP is a tool designed to retrieve comments from Bilibili videos using the Model Context Protocol (MCP).

How to use Bilibili Comments MCP?

To use this tool, clone the repository from GitHub, install the necessary dependencies, and configure the MCP client with your Bilibili cookie.

Key features of Bilibili Comments MCP?

  • Retrieve comments from Bilibili videos with support for pagination and nested replies.
  • Customizable parameters for sorting and filtering comments.
  • Easy setup with clear instructions for configuration.

Use cases of Bilibili Comments MCP?

  1. Analyzing viewer feedback on specific videos.
  2. Collecting comments for sentiment analysis.
  3. Archiving comments for research purposes.

FAQ from Bilibili Comments MCP?

  • How do I get my Bilibili cookie?

Log in to the Bilibili website, open developer tools, and copy the cookie value from the request headers.

  • Is this tool free to use?

Yes! Bilibili Comments MCP is open-source and free to use for everyone.

  • Can I retrieve comments from any video?

Yes, as long as you have the video ID (bvid or aid) and the necessary cookie.

Server Config

{
  "mcpServers": {
    "bilibili-comments": {
      "command": "node",
      "args": [
        "/path/to/bilibili_mcp.js"
      ],
      "env": {
        "BILIBILI_COOKIE": "your_bilibili_cookie_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
222wcnm
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago