M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBilibili MCP ServerA local MCP server for AI agents to read Bilibili subtitles and commentsBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS64 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Creators or researchers who want AI assistants to extract text content from Bilibili videos
  • Users who need to batch organize Bilibili favorites or subtitle data
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users not willing to provide Bilibili Cookie credentials
  • Anonymous use cases without accessing private content such as favorites
  • Users requiring long transcriptions that exceed resource limits
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires Bilibili login credentials (Cookie) for features like search and favorites
  • Credentials stored locally in config file (~/.bilibili-mcp/config.json)
  • Requests are sent only to official Bilibili endpoints
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Credentials stored locally without OS-level encryption
  • High-frequency calls may trigger Bilibili risk control or rate limiting
  • This is a third-party tool, not an official Bilibili service
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools911