About rippr
rippr extracts YouTube transcripts for people and AI agents, with a website, Chrome extension, and local MCP server. It offers clean text, structured JSON, and Markdown outputs, using multiple extraction methods.
Key features
- 01Extract YouTube transcripts
- 02Output clean text, JSON, or Markdown
- 03Use a website or Chrome extension
- 04Save MCP transcripts to a local folder
- 05Try multiple extraction strategies
Use cases
- 01Get a transcript from a YouTube URL
- 02Extract captions while viewing a YouTube page
- 03Prepare transcript text for chunking and embedding
- 04Provide timestamped transcript data to an AI client
MCP support
The local stdio MCP server connects to compatible desktop clients and returns the saved transcript's file path. Transcripts are stored in `~/rippr/transcripts/`.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
1Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | YouTube video URL. Supports any YouTube URL format (watch, youtu.be, embed, shorts, or bare 11-char ID). |
| format | enum | No | Saved file format. 'text' writes a Markdown file with YAML frontmatter and a continuous transcript block (best for RAG/LLM). 'segments' writes a JSON file with timestamped segments (best for chapter markers, precise citations). Default: text.text | segments |
| save_path | string | No | Optional override for where to save the transcript. Can be an absolute path, a ~/-relative path, a directory (file is named automatically), or a full file path. When you save outside the default directory, the returned resource_link still points to the saved file so it can be read later. Default: ~/rippr/transcripts/<slug>_<videoId>.<ext> |
| return_text | boolean | No | If true, include the full transcript text in the tool response alongside the resource_link. Default: false. Use true only for short clips or when the user explicitly wants the transcript inline. |
Details
From the project README
rippr
YouTube transcript ripper for humans and AI agents.
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.
npx rippr-mcp
Add to Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"rippr": {
"command": "npx",
"args": ["-y", "rippr-mcp"]
}
}
}
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
| MCP | What it does |
|---|---|
| Japan UX | Japanese UX rules for AI: forms, keigo, typography, trust signals |
| Rakuten | Search Rakuten's marketplace, books, and hotels |
| Xendit | Xendit payment APIs: invoices, disbursements, balances |
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.