tubearchivist-mcp
Related Servers
Alternatives to tubearchivist-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceConnects to a self-hosted Dashy dashboard's REST API to inspect system health, schema, and configuration files, and to perform confirm-gated edits such as adding, updating, or deleting sections and items. Writes are dry-run by default and require an allow-writes gate plus explicit confirmation, with tokens redacted from all output.5MIT
- AlicenseAqualityBmaintenanceConnects an MCP client to a self-hosted Ampache 8.4.0 server through its JSON API, enabling library browsing and search, playlist and smartlist management, catalog tasks, shares, podcasts, and user administration. Writes are gated behind a boolean confirm flag plus an explicit allow-writes setting, and secrets such as API keys, session tokens, and passwords are redacted from responses.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with self-hosted Miniflux instances through the HTTP API, covering feeds, categories, entries, enclosures, icons, OPML, users, and API keys. Write operations are confirm-gated with dry-run previews and secret redaction.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching YouTube Music and managing playlists through read and confirmation-gated write tools over STDIO. Supports identity checks, song search, playlist listing/retrieval, and previewed playlist creation, track addition, and exact track removal.MIT
- 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 14 tools
Each tool is scoped to a distinct resource domain (channel, video, playlist, download, task, config, etc.), so most selections are unambiguous, and the embedded action lists plus HTTP endpoints further disambiguate. A few edges blur: ta_system.notifications (in-app) versus ta_notify (webhook URLs on scheduled tasks), and ta_library.refresh (reindex) versus ta_maintenance.rescan versus ta_task.start, could be confused by an agent.
All 14 tools follow an identical ta_<resource> pattern with singular resource nouns, and sub-operations are consistently expressed as named actions inside each tool. No camelCase/snake_case mixing or ad-hoc verb prefixes anywhere.
14 tools is squarely in the well-scoped range and maps one-to-one onto TubeArchivist's resource domains rather than exposing each of the ~70 REST actions as a separate tool. The grouping keeps the surface navigable without omitting functionality.
Coverage is unusually thorough: full CRUD for channels, playlists (including custom), downloads, tasks and schedules, snapshots/backups, config/cookies, user prefs, plus stats, search, subtitles and watched-state. Minor gaps remain — no operation to add an individual video to a custom playlist, comments are read-only, and there is no search-suggestion/autocomplete action.