audiobook_mcp
Related Servers
Alternatives to audiobook_mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns PDF or EPUB books into reusable AI analysis, Obsidian notes, and agent Skills that can be installed into Codex, Claude Code, or other MCP clients.38MIT
- FlicenseNot gradedqualityCmaintenanceConverts large comic archives (CBZ/CBR) into Kindle-optimized EPUB volumes with GPU acceleration, smart chunking under Amazon's 200MB limit, and device-specific profiles for manga/comics.-
- FlicenseNot gradedqualityFmaintenanceHosted Streamable HTTP MCP server (https://epublys.com/mcp) with 9 tools for EPUB/PDF manipulation: merge, split, compress, EPUB↔PDF conversion, metadata read/edit, validation with auto-fix, and AI cover generation. Free API key, no install. Listed on the official MCP registry as com.epublys/epublys.-
- AlicenseNot gradedqualityCmaintenanceTranscribes audio/video files, generates summaries and structured knowledge items, and supports Notion integration and chat-based interaction. Works as a standalone CLI, Notion integration, or MCP server tool for agent ecosystems.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables chat-driven audio analysis and enhancement using local Claude, including denoising, EQ, compression, and loudness normalization, with an A/B viewer for synchronized comparison.1MIT
- AlicenseAqualityCmaintenanceEnables local EPUB reading with AI agents, supporting annotations, parallel editions, and MCP tools.7AGPL 3.0
TDQS
Scored across 15 tools
Each tool targets a distinct operation: job lifecycle, status, boundary inspection/correction, output verification, and metadata handling are all clearly separated. Even similar tools like continue_conversion and run_until_done are explicitly differentiated by chunked vs. looping behavior.
All tools use the consistent audiobook_ prefix followed by verb_noun snake_case names (start_conversion, get_status, patch_chapter_boundary). This makes the intended action and target resource predictable across the entire toolset.
At 15 tools, the server is at the upper end of a well-scoped set, but every tool serves a distinct and necessary purpose in the audiobook pipeline. The count feels appropriate for covering conversion, progress tracking, boundary QA, verification, and metadata enrichment without redundant clutter.
The toolset provides a complete workflow: inspect EPUB, start/resume/run/cancel jobs, monitor progress, verify output, handle boundary corrections, and fetch/embed cover metadata. There are no obvious dead ends or missing lifecycle operations for the stated audiobook conversion purpose.