claudio-audiobook 0.1.4: paths never read the environment

Security hardening release. Audiobooks are made exactly as in 0.1.3.

• Paths no longer read the environment. output_dir, file and cover now expand only the home folder (~, $HOME, ${HOME}, and the Windows forms). Before, os.path.expandvars would expand any environment variable in a path, so a path like /tmp/$SECRET could read a secret into a folder name. Covered by tests.
• README Privacy section now also mentions that installing the package uses the network (PyPI), besides the one-time model download.

Install the extension: download claudio-audiobook-0.1.4.mcpb below and open it in Claude Desktop (Settings → Extensions). Start a new chat afterwards.

Full changelog: CHANGELOG.md

claudio-audiobook 0.1.3: on PyPI, registry marker, plugin lockfile

Packaging and documentation release. No change to how audiobooks are made, so the Claude Desktop extension behaves the same as 0.1.2.

• On PyPI with the MCP Registry marker. claudio-audiobook installs with uvx --from claudio-audiobook claudio-audiobook-mcp or uv tool install claudio-audiobook. The package README carries the mcp-name line the official MCP Registry reads, and server.json is included.
• Claude Code plugin: an icon, and a size-limited uv.lock next to pyproject.toml; the launcher pins the PyPI version.
• README: a chapters card built from the metadata of a real m4b, PyPI install lines, no pipe-to-shell install commands.
• Tests: the home-folder tests now pass on Windows. CI is green on Linux, macOS and Windows.
• Safety: the source distribution is an explicit allow-list, so local notes and settings can never be published.

Install the extension: download claudio-audiobook-0.1.3.mcpb below and open it in Claude Desktop (Settings → Extensions). Start a new chat afterwards so the assistant sees the current tool list.

Full changelog: CHANGELOG.md

claudio-audiobook 0.1.2: tags, cover art, more MCP clients

What's new

Audiobook tags and cover art. The m4b (and mp3) now carries what players use to file it under Audiobooks: title, author, narrator, album, genre "Audiobook", the audiobook media type, and an embedded cover.

• Cover art, made locally. A title cover is generated on your machine (no network). Your AI assistant can choose its colours (cover_colors), or you give your own .jpg/.png (cover), or drop a cover.jpg in the book's folder, or use cover=none.
• New settings author, narrator, cover, cover_colors: CLI flags, MCP arguments, and an author default in the Claude Desktop extension settings.
• Repackaging is instant. Changing the format, author or cover only repackages the existing chapters. Nothing is rendered again.
• Works with other MCP clients. README now has setup for Cursor, VS Code (Copilot), Gemini CLI and Codex CLI. Optional tool parameters are advertised as plain types instead of anyOf [T, null], which Cursor and Gemini mishandle. Not yet run inside those tools.
• Better guidance for the AI: default to m4b (chapter list), and say that mp3 and wav have no chapters.
• New dependency: pillow.

Install

• Claude Desktop: download claudio-audiobook-0.1.2.mcpb below and open it (Settings → Extensions). Upgrading over 0.1.1 keeps your settings. A "Missing server configuration" toast may flash once during the swap; the server reconnects a moment later.
• Claude Code: /plugin marketplace add restante/claudio_audiobook
• Start a new chat after upgrading so the assistant sees the new tool arguments.

Tested

Claude Desktop (installed and rendered from this build), BookPlayer on iOS (chapters, tags and cover). VLC for iOS plays it but did not show the chapter list. 72 automated tests.

Full changelog: CHANGELOG.md

claudio-audiobook 0.1.1

First release. Create audiobooks locally with Kokoro voices from Claude Desktop or Claude Code: say "create a python course audiobook".

Claude Desktop: download claudio-audiobook-0.1.1.mcpb below and open it with Claude Desktop (Settings > Extensions). Dependencies install automatically; the voice model (about 330 MB) downloads once on first use.

Claude Code: see the README for the plugin install.

Everything runs on your computer; nothing is uploaded.