Bilibili History MCP
Apps & Automationbilibili-history-mcpBilibili History MCP is an Agent Skill for apps & automation published in the LifeArchiveProject/BilibiliHistoryFetcher repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when an AI client needs to read BilibiliHistoryFetcher data through its read-only LAN MCP server without loading the full project context.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/LifeArchiveProject/BilibiliHistoryFetcher/blob/HEAD/skills/bilibili-history-mcp/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/bilibili-history-mcp, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Bilibili History MCP
Use the project's MCP server instead of reading files directly when the user asks for local Bilibili history, yearly reports, viewing analytics, interaction records, video details, scheduler status, or data health.
Start Here
- Read
bili://project/overview. - Read
bili://project/data-status. - Read
bili://project/tool-guideonly when choosing a tool is unclear.
Tool Rules
- Prefer summary tools before record tools.
- Always paginate record tools; keep
sizesmall unless the user asks for bulk analysis. - Use
query_history_recordsfor browsing andsearch_history_recordsfor keyword lookup. - Use
get_annual_summary,get_viewing_analytics, andget_title_analyticsfor analysis. - Use
query_interaction_recordsonly afterget_interaction_summarywhen details are needed. - Do not ask for write operations; this MCP intentionally does not expose sync, fetch, download, delete, login, reset, or config update.
Privacy
The MCP is LAN HTTP with Bearer Token auth. Treat returned watch history as private user data. Do not request secrets such as SESSDATA, bili_jct, email passwords, or config tokens.