ai.com.mcp/lenny-rachitsky-podcast · v0.6.0 · ai-and-media
Lenny Rachitsky Podcast Transcripts MCP Server is healthy: it completed an MCP handshake in 805 ms and exposes 8 tools.
MCP server for structured access to Lenny Rachitsky podcast transcripts. For content creators.
Endpoint: https://lenny-rachitsky.run.mcp.com.ai/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 8 |
| Latency | 805 ms |
| Last checked (UTC) | 2026-10-16T22:20:38.517Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T22:20:38.517Z | Healthy | 805 | |
| 2026-10-15T15:15:28.722Z | Healthy | 1866 | |
| 2026-10-14T08:59:55.155Z | Healthy | 872 |
getEpisodes | List episodes - Lists episodes with parsed frontmatter (guest, title, duration, youtube_url, etc.) and their canonical resource URIs. |
getEpisodesGuest | Get an episode card (metadata + key URIs) |
getEpisodesGuestMetadatajson | Get episode metadata as JSON (frontmatter) |
getEpisodesGuestTranscriptformat | Get transcript in a specific format - Returns the transcript in the requested format: - md: markdown (may include or exclude frontmatter based on include_frontmatter) - txt: clean text (best for LLM ingestion) - json: structured form (metadata + transcript text) |
getEpisodesGuestChunks | List chunk descriptors for an episode - Returns chunk boundaries and URIs for chunk retrieval. Chunks may be computed on-demand using size/overlap parameters. |
getEpisodesGuestChunksChunkIdtxt | Get a specific transcript chunk as plain text |
getSearch | Search episodes and transcripts - Searches across metadata (D1) and transcript text (Vectorize). Returns matches as resources, including per-hit URIs pointing to episode cards and transcript chunks. Note: pagination cursor applies to metadata search only. Example (vector search with filters): GET |
postSearch | Search episodes and transcripts (POST body) - Same search as GET /search, but parameters are provided in the request body. This is useful for longer filter payloads. |