audio-story-mcp
Related Servers
Alternatives to audio-story-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables Claude Code to retrieve YouTube transcripts, search videos and channels, fetch metadata, playlists, comments, trending videos, engagement analytics, chapters, SponsorBlock-cleaned transcripts, and most-replayed heatmaps.1516 npm-
- AlicenseAqualityDmaintenanceEnables YouTube integration with Claude Code, including video search, metadata retrieval, transcript fetching, channel exploration, and trending videos.81MIT
- FlicenseNot gradedqualityDmaintenanceEnables transcription, search, and lesson generation from podcast and YouTube URLs directly inside Claude Code.2-
- FlicenseAqualityCmaintenanceEnables Claude Code to access YouTube features such as video transcripts, search, metadata, channel info, playlists, comments, trending videos, engagement analytics, chapters, SponsorBlock, and most-replayed heatmaps.1516 npm1-
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered YouTube content management using Claude Code to orchestrate research, scripting, and scheduling via Google Sheets, Docs, and Drive.-
- FlicenseNot gradedqualityCmaintenanceEnables Claude Code to search YouTube, retrieve video transcripts and metadata, explore channels, playlists, comments, and trending videos, and analyze engagement and replayed segments.16 npm-
TDQS
Scored across 11 tools
The tools generally map to distinct pipeline stages: fetch, transcribe, validate, voice selection, TTS render, QA, assembly, and diagnostics. There is some sequential overlap between fetch_source/transcribe and tts_preview/tts_render, but the descriptions make the intended usage clear.
All tool names use snake_case and most follow a verb_noun pattern such as list_runs, fetch_source, check_script, and assemble_audio. Minor deviations like run_status, transcribe, tts_preview, tts_render, qa_audio, and doctor are still readable and predictable by domain context.
Eleven tools is well within a reasonable range for an end-to-end audio story production pipeline. Each tool corresponds to a meaningful stage or utility, and none appear obviously redundant.
The surface covers the main audio workflow: source intake, transcription, script validation, voice listing, TTS preview/render, QA, assembly, and environment diagnostics. Minor gaps remain around explicit script/cast authoring and run cleanup/deletion, though these may be handled by external file tools.