ampache-mcp
Related Servers
Alternatives to ampache-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceConnects MCP clients to a self-hosted photo library through its REST API, exposing assets, albums, people, search, and optional administrative toolsets with read-only defaults and confirm-gated writes. It supports stdio and localhost Streamable HTTP transports.587 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients to interact with a self-hosted comic/library server through its HTTP API, exposing libraries, series, books, collections, readlists, metadata, and administrative operations with read/write safety controls over stdio or Streamable HTTP.7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to manage a self-hosted Zipline instance's files, folders, short URLs, invites, tags, and account or instance information through the official JSON API, with confirmation-gated writes and redacted secrets.6174 npmMIT
- AlicenseAqualityBmaintenanceConnects MCP clients to a self-hosted Syncthing instance's GUI REST API for reading configuration, folders, devices, and connections, plus gated write actions like adding or patching folders and devices, scanning, pausing, restarting, and shutting down. Supports stdio and localhost-only Streamable HTTP with API-key auth, dry-run write previews, redaction of secrets, caching, and rate limiting.5MIT
- AlicenseAqualityCmaintenanceEnables managing a self-hosted media library through its HTTP API, with scoped toolsets, confirm-gated writes, dry-run previews, and read caching. Supports libraries, items, collections, playlists, podcasts, sessions, stats, tags, genres, and administrative operations.13131 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.9 npmMIT
TDQS
Scored across 7 tools
The tools are grouped into clear domains (system, library, playlists, catalogs, shares, podcasts, users), so most selections are straightforward. However, ampache_catalogs bundles catalog management with song-level actions like flag, rate, scrobble, song_delete, and update_art that conceptually overlap with ampache_library, and ampache_system's generic browse/list actions can be confused with library browsing.
All seven tools follow a consistent ampache_<domain> lowercase snake_case pattern. Minor singular/plural variation (ampache_library vs. ampache_playlists) is natural for uncountable domains and does not create confusion.
Seven tools is well within the ideal range, and each domain category earns its place. The action-dispatch design keeps the exposed tool count manageable while covering a broad API.
Coverage spans system/session operations, library browsing and search, playlists and smartlists, catalogs, shares, podcasts, users, and preferences, including admin preference operations. No obvious lifecycle gaps exist for an Ampache API client.