Bilibili Subtitle Fetch

Created By
Initsnowa year ago
MCP server for fetching Bilibili video subtitles with language and format options.
Overview

What is Bilibili Subtitle Fetch?

Bilibili Subtitle Fetch is an MCP server designed to fetch subtitles for Bilibili videos, offering options for language and format.

How to use Bilibili Subtitle Fetch?

To use Bilibili Subtitle Fetch, install the dependencies, set the required environment variables with your Bilibili credentials, and run the server with your preferred language and output format.

Key features of Bilibili Subtitle Fetch?

  • Fetch subtitles from Bilibili videos in various languages.
  • Support for different output formats (text or timestamped).
  • Easy configuration through environment variables and CLI arguments.

Use cases of Bilibili Subtitle Fetch?

  1. Fetching subtitles for Bilibili videos in different languages.
  2. Converting subtitles into various formats for accessibility.
  3. Integrating subtitle fetching into other applications or services.

FAQ from Bilibili Subtitle Fetch?

  • What credentials do I need to use Bilibili Subtitle Fetch?

You need to provide Bilibili credentials such as sessdata, jct, and buvid3.

  • Can I choose the language of the subtitles?

Yes! You can set your preferred language using environment variables or CLI arguments.

  • What output formats are supported?

The tool supports both text and timestamped formats for subtitles.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Initsnow
Star
0
Language
Python
License
GPL-3.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago