bilibili

This MCP server implements a Go-based Bilibi Li (bilibili) MCP service that can run in SSE or stdio modes. It exposes tools to interact with Bilibili data such as querying your personal profile information, listing your latest follows (requires login), and searching videos. To use private data endpoints, you need to provide a configuration file containing your Bilibili cookie and start the MCP server with the path to that config as the first argument. The server will read the cookie and use it for authenticated requests. Example usage with the provided binary: D:\bili\Bilimcp.exe D:\bili\config.yml. In the config.yml, include your Cookie value (and any other needed fields) so the server can access your private data when requested by tooling.

Prerequisites:

• Access to the Bilimcp Go-based MCP server binary (either download a prebuilt binary for your OS or build from source).
• A Bilibili account and a valid cookie if you plan to query private information.

Installation steps:

1. Download or build the MCP server binary
   • Download: Obtain the Bilimcp.exe (or corresponding binary for your OS) from the release page.
   • Build from source (Go installed): go env -w GOPROXY=https://proxy.golang.org go build -o Bilimcp.exe ./path/to/source
2. Prepare a configuration file with your Bilibili cookie
   • Create config.yml containing your cookie, for example: Cookie: your_cookie_value_here
3. Run the server with the config path as the first argument
   • Example (Windows): D:\bili\Bilimcp.exe D:\bili\config.yml
   • If running on other platforms, ensure the executable path and config path are valid and accessible.
4. Verify the server is running by connecting via SSE or stdio as documented by the project.

• The config.yml file is expected to contain your Bilibili Cookie. Do not expose this file publicly as it grants access to private data.
• The server supports both SSE and stdio modes for integration with MCP clients; choose the method that best fits your deployment.
• If you encounter login-related issues, ensure the cookie is current and that any required login scope permissions are granted.
• When upgrading, replace the binary and retain your config.yml to preserve cookies and settings.
• If you need to run multiple instances, duplicate the config and use distinct server entries in mcp_config with their corresponding executable paths.
• Environment variables can be used for additional configuration (not required for basic operation).