Bilibili Video Info MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSDATA | Yes | Your valid Bilibili SESSDATA cookie value, found in browser developer tools under Application/Storage -> Cookies. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_subtitlesA | Get subtitles from a Bilibili video |
| get_danmakuA | Get danmaku (bullet comments) from a Bilibili video |
| get_commentsA | Get popular comments from a Bilibili video |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose targeting different aspects of video content: comments, danmaku (bullet comments), and subtitles. There is no overlap in functionality, and the descriptions make it easy to differentiate between these three types of video metadata.
All tools follow a consistent 'get_noun' pattern (get_comments, get_danmaku, get_subtitles) using snake_case throughout. This predictable naming convention makes it easy for agents to understand what each tool does based on its name alone.
With only 3 tools, the server feels somewhat thin for a video information domain. While the tools cover specific metadata types well, there are likely other relevant operations (like getting video details, statistics, or user info) that would make the surface more complete for typical video analysis workflows.
The toolset has significant gaps for a video information server. There's no way to get basic video metadata (title, description, duration, uploader), statistics (views, likes, shares), or user information. While the three tools provide specific content types, they don't cover the fundamental video information that would typically be needed first in most workflows.