get_podcast_latest — AudioAlpha MCP Tool Read-only
get_podcast_latest
(get podcast latest) is one of 23 tools on the
AudioAlpha
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_podcast_latest from your client
- Claude Code AudioAlpha get_podcast_latest run in your project directory
- Claude Desktop AudioAlpha get_podcast_latest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AudioAlpha get_podcast_latest ~/.cursor/mcp.json
- VS Code AudioAlpha get_podcast_latest .vscode/mcp.json
- Zed AudioAlpha get_podcast_latest ~/.config/zed/settings.json
- Windsurf AudioAlpha get_podcast_latest ~/.codeium/windsurf/mcp_config.json
- Cline AudioAlpha get_podcast_latest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AudioAlpha get_podcast_latest ~/.gemini/settings.json
- Grok AudioAlpha get_podcast_latest .mcp.json (in your project root)
- ChatGPT AudioAlpha get_podcast_latest Settings → Connectors → Advanced → Developer mode
- Claude.ai AudioAlpha get_podcast_latest Settings → Connectors → Add custom connector
- LangChain AudioAlpha get_podcast_latest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.audioalpha.io/api/mcpOther tools on this server
- get_market_snapshot
- get_market_themes
- get_market_signals
- get_market_featured_quotes
- get_market_episodes
- get_market_history
- get_ticker_snapshot
- get_ticker_signals
- get_ticker_featured_quotes
- get_ticker_history
- get_ticker_leaderboard
- search_podcasts
- get_podcast_episodes
- get_podcast_latest_full
- get_episode_details
- get_episode_summary
- get_episode_quotes
- get_episode_transcript
- get_episode_full
- get_my_favorite_assets
- get_my_favorite_podcasts
- get_my_feed
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.