Skip to content

Usage — API / CLI / MCP

audiobookshelf-mcp exposes the same capability three ways: as MCP tools an agent calls, as a Python API the operator import, and as a CLI.

As an MCP server

Once deployed, the server registers consolidated, action-routed tool modules. Each module is independently togglable with a *TOOL environment flag.

As a Python API

from audiobookshelf_mcp.auth import get_client

api = get_client()  # resolves AgentConfig/runtime connection and verified TLS trust
try:
    libraries = api.get_libraries()
finally:
    api.close()

As a CLI

# AUDIOBOOKSHELF_URL and AUDIOBOOKSHELF_TOKEN are injected by the runtime.
audiobookshelf-mcp --transport stdio

The server exposes one typed tool per Audiobookshelf API operation (library, item, author, series, podcast, user, progress, session, collection, playlist, backup, email, notification and server tools, each prefixed audiobookshelf_). Enable only the operations authorized for the connector identity.

When catalog metadata must enter epistemic-graph, request centrally governed Arbora source synchronization. The provider exposes no direct graph-write or raw-cover ingestion action. See Configuration, trust, and privacy.