WatermelonFin MCP
Related Servers
Alternatives to WatermelonFin MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agent clients to index and organize local media libraries by recognizing codes from filenames, querying media, checking library quality, adding files, fetching metadata, and scanning directories, with deletion gated by verified magnet links.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to search and browse an Immich photo library by content or metadata, inspect EXIF/people/albums/tags, view images and contact sheets, analyze duplicates and activity, and export browser-ready files with manifests. With an optional write key, it also enables curation such as favorites, ratings, descriptions, tags, albums, people, uploads, and reprocessing.MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to read and draft Proton Mail messages, browse and download Proton Drive files, and read calendar agendas or prepare import files through local connections. Mail sends and Drive uploads stay disabled until explicitly enabled and verified.MIT

gaiadesk-mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants and MCP clients to execute commands, copy/move files, manage background jobs and port forwarding, and optionally view and control remote screens using scoped, expiring agent tokens.8 npm1MIT- AlicenseAqualityAmaintenanceEnables AI assistants to browse an entire media server library—watched and unwatched items, per-user watch history, continue-watching, recommendations, and library statistics—alongside safe curation writes such as playlists, collections, ratings, watched state, and the plex.tv watchlist. Optional playback control and Tautulli statistics extend it, while a read-only mode removes every write.22213 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables self-hosted remote access to a user-controlled device's approved filesystem roots, allowing clients to list directories, read and search files, inspect metadata, ping the agent, and list devices through an MCP tunnel.AGPL 3.0
TDQS
Scored across 17 tools
Most tools have clearly distinct resource/action targets, especially upload, metadata revision, discovery, and connection inspection. The main possible confusion is among the several inspect_* tools and the metadata refresh/restore/inspect family, but their descriptions sufficiently distinguish ownership, scope, and side effects.
All tools use snake_case and follow a predictable verb_noun pattern such as upload_media, list_libraries, inspect_connection, and restore_import_metadata. The convention is consistently applied throughout the set.
Seventeen tools is slightly heavy but still reasonable for a server covering authentication, discovery, upload, metadata lifecycle, artwork, search, and connection inspection. Each tool appears to serve a distinct operational need rather than duplicating functionality.
The server covers the core lifecycle well: discovery, authentication, library/target listing, upload, metadata inspection/update/restore/refresh, artwork, search, and connection export/inspection. Deletion and broader media administration are absent, but that appears intentional given the safety-focused scope.