A
licenseB
qualityC
maintenanceA Model Context Protocol server that allows AI assistants to retrieve user information, search videos by ID, and find content by keywords on bilibili.com.
3
48
15
MIT
Bilibili-Api
Provides tools for accessing Bilibili's API, enabling retrieval of user information, video details, and video search functionality on the Bilibili platform.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bilibili-Apisearch for videos about machine learning tutorials"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
B站API服务器 Bilibili Api
一个为bilibili.com API提供服务的Model Context Protocol (MCP)服务器，支持获取用户信息、视频搜索等功能。 A Model Context Protocol (MCP) server that provides services for the bilibili.com API, supporting functions such as obtaining user information and video search.## 工具列表 Tool List
本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。
工具 Tool | 描述 Description |
get_user_info | Get information about a Bilibili user |
get_video_info | Get detailed information about a Bilibili video |
search_videos | Search for videos on Bilibili |
检查服务 ## Inspector
工具在线测试： https://mcp.xiaobenyang.com/inspector/1777316659451907
Online Tool test https://mcp.xiaobenyang.com/inspector/1777316659451907
Related MCP server: Bilibili MCP Server
服务配置 MCP Server Config
如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?
访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.
SSE
{
"mcpServers": {
"B站API服务器": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "sse",
"url": "https://mcp.xiaobenyang.com/1777316659451907/sse"
}
}
}STREAMABLE HTTP
{
"mcpServers": {
"B站API服务器": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "streamable_http",
"url": "https://mcp.xiaobenyang.com/1777316659451907/mcp"
}
}
}STDIO
{
"mcpServers": {
"B站API服务器": {
"command": "npx",
"args": [
"-y",
"xiaobenyang-mcp"
],
"env": {
"XBY_APIKEY": "<YOUR_XBY_APIKEY>",
"mcpId": "1777316659451907",
},
"transport": "stdio"
}
}
}
Available Tools
3 toolsget_user_infoget_user_infoC
Get information about a Bilibili user
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mid | Yes |
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't cover key traits like whether it's read-only, requires authentication, has rate limits, or what the response format includes. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't provide enough context for an agent to effectively use the tool, missing details on parameters, behavior, and output, which are critical for a tool with one required parameter.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, and the description doesn't add any meaning beyond the schema. It doesn't explain what 'mid' represents (e.g., user ID), its format, or constraints, failing to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Get') and resource ('information about a Bilibili user'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_video_info' or 'search_videos' beyond specifying the resource type, missing explicit distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as needing a user ID, and doesn't mention sibling tools or scenarios where other tools might be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_video_infoget_video_infoC
Get detailed information about a Bilibili video
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bvid | Yes |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get detailed information' implies a read-only operation, it doesn't specify whether this requires authentication, rate limits, what kind of information is returned, or error handling. The description is too vague for a tool with no annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't explain what 'detailed information' includes, how to interpret the bvid parameter, or any behavioral aspects. For a tool with this complexity and lack of structured support, it should provide more context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'Bilibili video' which hints that 'bvid' is a video identifier, but doesn't explain format, examples, or constraints. This adds minimal value beyond the schema, meeting the baseline for low coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'detailed information about a Bilibili video', making the purpose specific and understandable. It distinguishes from siblings like get_user_info (user-focused) and search_videos (search-focused), though it doesn't explicitly mention this distinction in the text.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like search_videos or get_user_info. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent to infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_videossearch_videosC
Search for videos on Bilibili
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | ||
| page | No | ||
| count | No |
TDQS
C2.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states the basic action without any details on traits like rate limits, authentication requirements, response format, or error handling. For a search tool with no annotation coverage, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with a single sentence, 'Search for videos on Bilibili', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, making it easy to scan and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a search tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how results are structured, or any behavioral aspects like pagination or error cases. This leaves critical gaps for an AI agent to use the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, meaning none of the parameters (keyword, page, count) are documented in the schema. The description adds no information about these parameters, such as what 'keyword' should contain, how 'page' and 'count' affect pagination, or their default values. This fails to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Search for videos on Bilibili' clearly states the action (search) and resource (videos on Bilibili), making the basic purpose understandable. However, it lacks specificity about what kind of search it performs (e.g., keyword-based, relevance ranking) and doesn't differentiate from potential sibling tools like 'get_video_info', which might retrieve specific videos rather than search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like searching by keyword, pagination needs, or how it differs from sibling tools such as 'get_user_info' or 'get_video_info'. Without this context, users must infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
C2.9/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: get_user_info targets user data, get_video_info targets video metadata, and search_videos targets video discovery. There is no overlap in functionality, making tool selection unambiguous for an agent.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes and snake_case formatting. This predictable naming scheme enhances readability and usability across the set.
Tool Count3/5
With only 3 tools, the set feels thin for a Bilibili API server, which might be expected to handle more operations like comments, playlists, or uploads. However, it covers basic user, video, and search functions adequately for a minimal scope.
Completeness3/5
The tools provide read-only access to users, videos, and search, but lack CRUD operations (e.g., no create, update, or delete) or broader API coverage like comments or subscriptions. This limits agents to informational tasks without full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
BGG MCP provides access to the BoardGameGeek API through the Model Context Protocol, enabling retr…
MCP server for Hailuo (MiniMax) AI video generation
MCP server for meme generation, template search, caption rendering, and AI meme creation.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server that enables users to search Bilibili videos, access trending rankings, and retrieve detailed information about videos, content creators, and anime schedules. It allows AI applications to interact directly with Bilibili content via simple API interfaces.69192MIT
- AlicenseBqualityDmaintenanceA MCP server providing 22 tools to interact with Bilibili API, enabling video info, search, user profile, comments, rankings, and messaging with login support for write operations.223GPL 3.0
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides tools for parsing and retrieving Bilibili video information, including video details, download links, and collection listings.5131
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xiaobenyang-com/1777316659451907'
If you have feedback or need assistance with the MCP directory API, please join our Discord server