
Rippr Mcp
io.github.mrslbtPublished by GitHub account mrslbtv1.3.0Updated Oct 25, 2026
Rip YouTube transcripts to disk for AI agents, RAG pipelines, and LLM workflows.
Overview
A local MCP server that fetches YouTube video transcripts and saves them to disk, returning the file path to the assistant.
- What you can do
- Fetch a YouTube video's transcript from a URL and save it under the local rippr transcripts folder, returning the file path to the model. Produce the transcript in RAG text, structured JSON with timestamped segments, or readable Markdown. Fall back across several extraction strategies (player API, page source, transcript panel) with retries when one fails.
- When to use it
- Useful when you want an assistant to pull YouTube transcripts into local files for RAG pipelines, LLM workflows, or note-taking, and you work in a desktop MCP client such as Claude Desktop, Claude Code CLI, or Cursor.
- Requirements
- Runs as a local stdio process started with npx from the npm package rippr-mcp, so Node.js and network access to YouTube are needed. Desktop MCP clients only; cloud-hosted or mobile clients cannot spawn it. No accounts or API keys.
Installation
In SourceWeft
- Open Rippr Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
rippr
YouTube transcript ripper for humans and AI agents.
[npm] [npm downloads] [Manifest V3] [MIT License] [LobeHub MCP] [Glama MCP]
Website · Chrome Web Store · MCP Server (npm)
Three ways to use rippr
🌐 Website — rippr.me
Paste a YouTube URL, get the transcript. Clean text, no signup.
🧩 Chrome Extension — Chrome Web Store
One-click transcript extraction directly on any YouTube page. Multiple output formats (RAG, JSON, Markdown).
🤖 MCP Server — npm
Connect rippr to Claude, Cursor, or any MCP-compatible client. Saves each transcript to ~/rippr/transcripts/ and returns the file path to the model.
Desktop clients only. rippr runs as a local stdio process, so it works with Claude Desktop, Claude Code CLI, and Cursor. It does not work with cloud-hosted clients (claude.ai on the web, the Claude mobile app, or Claude Code on phone / web), which can't spawn local processes.
Add to Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
Then ask: "Rip this YouTube video: [url]". See mcp/README.md for the full tool surface.
Output formats
- RAG (.txt) — single continuous text block, optimized for chunking and embedding
- Structured (.json) — timestamped segments with metadata
- Readable (.md) — markdown with headers and formatting
How it works
Multi-strategy extraction for maximum reliability:
- Innertube API — YouTube's internal player API (Android client)
- HTML scraping — parses
ytInitialPlayerResponsefrom page source - Transcript panel — opens YouTube's built-in transcript panel as last resort
Caption XML parsed in multiple formats (srv3, timedtext, JSON3). Retry with exponential backoff on transient failures.
Privacy
Runs entirely on your machine. No data sent to external servers. No accounts, no tracking. Only communicates with YouTube's own APIs.
More MCPs
Disclaimer
Rippr is an unofficial, community-built tool. It is not affiliated with, endorsed by, or sponsored by YouTube or Google LLC. YouTube is a trademark of Google LLC.
Rippr accesses publicly available YouTube transcript data through endpoints that YouTube's own apps use. Use is subject to YouTube's Terms of Service, and use is at your own risk. The author accepts no liability for takedowns, rate limits, account actions, or any other consequences of use.
If YouTube changes their internal APIs in ways that break extraction, the tool may stop working without notice. For long-term production use, consider the official YouTube Data API v3 with an API key (not currently supported by this package).
License
Source: README.md at commit c82845e
Tools
0Version history
1- v1.3.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts