bilibili-mcp-server

Bilibili-focused MCP Server (Go) that can run over SSE or stdio, providing AI-accessible tools for querying user information, fetching latest followed content (requires login), and searching videos.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp bilibili go sse stdio media-search personalization
⚙ Agent Friendliness
35
/ 100
Can an agent use this?
🔒 Security
29
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
45
Error Messages
0
Auth Simplicity
55
Rate Limits
10

🔒 Security

TLS Enforcement
40
Auth Strength
35
Scope Granularity
10
Dep. Hygiene
40
Secret Handling
20

Security is likely limited by cookie-based authentication: a long-lived session cookie in a local YAML file increases risk if leaked. README does not describe safe storage, redaction, logging behavior, or transport/security guarantees for SSE. No evidence of scoped/least-privilege access controls.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
40
Error Recovery
15
AF Security Reliability

Best When

You want to integrate Bilibili search and (optionally) logged-in personal data into an MCP-based agent workflow via stdio or SSE.

Avoid When

You cannot safely store/manage a Bilibili cookie or you require documented rate limits, robust error contracts, and strong operational guarantees.

Use Cases

  • AI agents that need to search Bilibili videos
  • Personalized assistants that read a user's profile or followed/latest content
  • Use in an MCP-capable chat/agent system to retrieve Bilibili-related data via tools

Not For

  • Applications needing a public REST/GraphQL API for web/browser clients
  • Use cases requiring fine-grained authorization beyond a stored Bilibili cookie
  • High-reliability production use without additional operational documentation/validation

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Bilibili cookie via YAML config passed as first CLI argument
OAuth: No Scopes: No

Authentication appears to rely on a Bilibili cookie stored in a local YAML config file for logged-in private data access.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Login-required tools depend on a valid cookie; expired/invalid cookies may cause failures that an agent should detect and handle.
  • No documented pagination/retry/idempotency behaviors in the provided README; agents may need to implement conservative retries and avoid repeated calls if side effects exist (unclear).
  • SSE vs stdio transport support is mentioned but without guidance on which is more reliable for the agent host.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for bilibili-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered