Install
"command": "npx",
"args": ["bilibili-mcp-js"]Who it is for
For people who need to retrieve Bilibili video content from the conversation instead of paging through a website. It offers searching a list of video blurbs, reading popular content, and viewing video details by BV or AV number. Official notes:
https://github.com/34892002/bilibili-mcp-js
Popular content covers overall popular, must-watch for newcomers, ranking boards, and the site-wide music board. If you want to edit uploads, post comments, or manage favorites, evidence does not cover those writes; do not treat it as a full Bilibili back office. There is also no account-login step, so do not assume you can see works visible only to you.
First try in 3 minutes
Take only one official install path: start package bilibili-mcp-js with npx in the MCP config.
"command": "npx",
"args": ["bilibili-mcp-js"]
Prerequisite: this machine's Node.js is not below 20.12.0. Evidence does not give a full config-file path or a required working directory; fill gaps from the client's existing MCP server entry. Do not invent unstated environment variables.
The first call is a read-only search: ask it to search Bilibili videos and return a list of content blurbs. Do not pass unstated filter fields, and do not look up a guessed BV number first.
Success signal: a set of video blurbs appears in the conversation, not a startup error. This queries the Bilibili side; it is not a no-network sandbox. Locally, npx also starts a process.
Use cases
Case 1: get a list of video blurbs by keyword. After config is live, start a search. What you can confirm is “search a list of video content blurbs”. Sort, paging, and partition codes are unwritten; if missing, stop at the blurb list and do not add unstated filter syntax.
Case 2: look up details when you already have a BV or AV number, or first view public popular content. Detail capability explicitly supports BV or AV numbers. Popular capability covers overall popular, must-watch for newcomers, ranking boards, and the site-wide music board. On success you should see detail fields or matching board rows. Evidence gives no tool names or parameter tables for these calls, so start the request from the capability description only; do not invent function names. If you have no BV/AV, take one of the four popular classes; do not invent a number to try.
Limits
Runtime floor is Node.js 20.12.0. There is also a source-start form: bun index.ts over stdio, TRANSPORT=remote bun index.ts over streamable HTTP. On the first try do not run those beside the npx config, and do not assume an HTTP port or auth method — those do not appear. Capabilities only write search, the four popular classes, and BV/AV details. Uploader profiles, anime schedules, or other writes are not in this evidence. With no login notes, do not put private favorites or upload management into the first request.