get_episode_details — PodLearn MCP Tool Read-only
get_episode_details
(get episode details) is one of 25 tools on the
PodLearn
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_episode_details from your client
- Claude Code PodLearn get_episode_details run in your project directory
- Claude Desktop PodLearn get_episode_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PodLearn get_episode_details ~/.cursor/mcp.json
- VS Code PodLearn get_episode_details .vscode/mcp.json
- Zed PodLearn get_episode_details ~/.config/zed/settings.json
- Windsurf PodLearn get_episode_details ~/.codeium/windsurf/mcp_config.json
- Cline PodLearn get_episode_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PodLearn get_episode_details ~/.gemini/settings.json
- Grok PodLearn get_episode_details .mcp.json (in your project root)
- ChatGPT PodLearn get_episode_details Settings → Connectors → Advanced → Developer mode
- Claude.ai PodLearn get_episode_details Settings → Connectors → Add custom connector
- LangChain PodLearn get_episode_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http podlearn https://httiyebjgxxwtgggkpgw.supabase.co/functions/v1/mcp-server-streamableOther tools on this server
- search_podcasts
- list_podcasts
- get_podcast_details
- search_episodes
- list_feed_episodes
- list_episodes
- transcribe_url
- transcribe_feed
- start_transcription
- get_transcription
- search_transcription
- get_transcription_segments
- list_lessons
- get_lesson_content
- generate_lesson
- get_subscription_status
- get_user_credits
- get_episode_usage
- get_saved_items
- save_item
- remove_saved_item
- generate_linkedin_post
- search_youtube
- browse_episodes
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.