Lenny Rachitsky Podcast Transcripts MCP Server
by lenny-rachitsky.run.mcp.com.ai in News & content
MCP server for structured access to Lenny Rachitsky podcast transcripts. For content creators.
https://lenny-rachitsky.run.mcp.com.ai/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 281 ms typical, 281 ms slowest 5%
- Last check
- 3 h ago
- Next check
- in 3 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"lenny-rachitsky-podcast-transcripts-mcp-server": {
"type": "http",
"url": "https://lenny-rachitsky.run.mcp.com.ai/mcp"
}
}
}8 tools
- 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 w
- 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.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 281 ms |