Skip to main content
Glama
Manny7717

flick

by Manny7717
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to flick

No user-submitted related servers found.

    Related Servers

    • Jellyseerr MCP Server

      aserper
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Jellyseerr media request systems through natural language. Supports searching for media, creating requests, checking request status, and managing your media library workflow.
      8
      -

    • Emby.MCP

      angeltek
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects an Emby media server to AI clients like Claude Desktop, enabling natural language control of media playback, library browsing, playlist management, and search across your personal media collection.
      10
      GPL 3.0

    • streamystats-mcp-server

      Barrow1990
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to interact with a self-hosted Streamystats Jellyfin dashboard, providing tools to list servers, search library items, manage watchlists, and check system status.
      MIT

    • plex-mcp-server

      aminamos
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes every documented Plex Media Server API operation as a callable tool, plus curated tools for library browsing, media search and editing, playlists, collections, live sessions, user analytics, recommendations, watchlists, playback control and subtitles. Enables clients to query, automate and control a Plex server, discover owned servers and control playback clients through natural language.
      124 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility: searching media, fetching metadata by ID, listing active sessions, listing top-level libraries, and showing next-up episodes. Search and info are related but role-separated by ID lookup, so an agent is unlikely to confuse them.

    Naming Consistency3/5

    The names are readable and all lowercase, but they are not pattern-consistent: search is a verb while info, sessions, and libraries are nouns, and next_up uses an underscore while the others do not. A uniform list_/verb_noun convention would make the set more predictable.

    Tool Count5/5

    Five tools is a well-scoped size for a focused Jellyfin browsing server. Each tool covers a meaningful high-level capability without overwhelming the agent with redundant operations.

    Completeness4/5

    The core read-only workflows for a Jellyfin assistant are covered: search, details, library listing, active sessions, and next episodes. Obvious minor gaps include browsing seasons/episodes within a show and playback controls, but these are not severe for the apparent purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources