Lenny's Podcast MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LENNY_TRANSCRIPTS_PATH | Yes | The local file system path to the directory containing the podcast transcripts. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_transcriptsA | Search across all of Lenny's Podcast transcripts for insights on a topic. Returns relevant excerpts from episodes with guest names. Use this to find what product leaders and experts have said about specific topics like pricing, growth, product management, hiring, etc. |
| get_episodeB | Get the full transcript for a specific episode by guest name. Use this when you want to dive deeper into a specific conversation. |
| list_episodesB | List all available episodes/guests in Lenny's Podcast archive. Use this to see what guests and topics are available to search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_episode retrieves a full transcript for a specific guest, list_episodes provides an overview of all available episodes, and search_transcripts finds relevant excerpts across all transcripts based on topics. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern with snake_case: get_episode, list_episodes, and search_transcripts. This predictable naming convention enhances readability and usability for agents.
With 3 tools, the server is well-scoped for a podcast archive, covering core operations like listing, retrieving, and searching. However, it might be slightly thin, as additional tools for metadata or episode details could enhance completeness, but the current count is reasonable for the domain.
The tool set covers essential CRUD-like operations for a podcast archive: listing episodes, getting specific transcripts, and searching across content. Minor gaps exist, such as no update or delete operations, but these are not critical for a read-only archive, and agents can work effectively with the provided tools.