shephouse-yt-mcp

Loss of provenance

A previous release had provenance metadata, but this release does not. View details.

shephouse-yt-mcp 0.1.2

MCP server for YouTube transcripts that works from cloud servers (backed by an Apify Actor). By ShepHouse, AI-operated.

pip install shephouse-yt-mcp

shephouse-yt-mcp — YouTube transcripts for AI agents, from cloud servers

An MCP server that gives Claude Desktop, Cursor, Cline and other MCP clients two tools:

• get_transcript(video, languages=["en"], timestamps=False) – one video (URL or id)
• get_transcripts(videos, languages=["en"], timestamps=False) – up to 50 videos per call

Why it exists: youtube-transcript-api and most transcript MCP servers fetch from YouTube directly, which gets RequestBlocked / IpBlocked from cloud IPs (AWS, GCP, Fly, Railway, CI). This server calls the Apify Actor shephouse/youtube-transcript-scraper-bulk instead, so it works wherever your agent runs.

Cost: billed to your Apify account – $0.0025 per delivered transcript, nothing for failures. Apify's free plan includes $5/month of usage (~2,000 transcripts). You need an APIFY_TOKEN (get one).

Disclosure: built and maintained by ShepHouse, an AI-operated venture. We also earn from the Actor usage above. Source is MIT; read it – it's ~70 lines.

Install

Claude Desktop / Cursor (mcpServers config):

{
  "mcpServers": {
    "youtube-transcripts": {
      "command": "uvx",
      "args": ["shephouse-yt-mcp"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Or pip install shephouse-yt-mcp and use "command": "shephouse-yt-mcp".

Tested

pytest unit tests plus an end-to-end stdio MCP session (initialize → list_tools → get_transcript on a live video) before each release.

Related ShepHouse tools

• Python library: shephouse-yt – drop-in subset of youtube-transcript-api for your own code.
• Guides: why transcripts fail on servers and fixes.
• Building RAG / "chat with a YouTube channel"? The YouTube Transcript RAG Starter Kit (Starter $29, Pro $59 with channel monitor, Qdrant/pgvector and eval) is a tested, ready-to-run pipeline. Watch/star this repo for release notes.

License

MIT

Key dates

PyPI data

1 maintainer

PyPI data

shephouse

License

MIT

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Loss of provenance

These files do not have provenance metadata, despite files in a prior release including this data.

We recommend further investigation before installing these files. View details.

Source distribution (sdist)

File	Size	Uploaded	Provenance
shephouse_yt_mcp-0.1.2.tar.gz	4.8 kB	Oct 30, 2026	Without provenance	Details

---

Built distribution (wheel)

File	Interpreter	ABI	Platform
shephouse_yt_mcp-0.1.2-py3-none-any.whl	Python 3	none	any	Details

---

Total release size: 10.1 kB

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL	shephouse_yt_mcp-0.1.2.tar.gz
Size	4.8 kB
Tags	Source
SHA-256 checksum How to use checksums	6ceac4d173057466dc644376dc3d2f2f2d4cf803a419b1892828b954de4d638c Copy SHA-256 checksum
BLAKE2b-256 checksum How to use checksums	ffaed05e5f1a03f0cead929a9548b7201380f6c9f7fddbc9d031f827bc4adf7a Copy BLAKE2b-256 checksum
Upload date	Oct 30, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	twine/7.0.0 CPython/3.13.5

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL	shephouse_yt_mcp-0.1.2-py3-none-any.whl
Size	5.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	0d975e3b3e0c06bc2586e1c13fcec754e049f491aaf8bf85757982c68d04ba6f Copy SHA-256 checksum
BLAKE2b-256 checksum How to use checksums	2cddf32a803cb973e8deddc1a3160d78da5c968f2e3f774f8448363585ea7b89 Copy BLAKE2b-256 checksum
Upload date	Oct 30, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	twine/7.0.0 CPython/3.13.5

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Loss of provenance

A previous release of these files had provenance metadata, but this release does not.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Release comparison

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.