Skip to main content
Glama
umsachde

simkl-mcp

by umsachde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to simkl-mcp

No user-submitted related servers found.

    Related Servers

    • Trakt MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables reading and writing Trakt data from Claude.ai and Claude Code, covering all 334 API endpoints including shows, movies, lists, calendars, scrobbling, and account sync.
      338
      MIT

    • Sonarr MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.
      234
      8 npm
      MIT

    • Plex-MCP

      ericwarthan
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables full management of a Plex Media Server via Claude, including browsing libraries, fixing metadata, managing collections, and more.
      -

    • TMDB MCP Server

      simentob
      F
      license
      A
      quality
      D
      maintenance
      Provides Claude AI with direct access to The Movie Database (TMDB) for searching movies, trending content, and reviews through natural language.
      6
      -
    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

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: auth (logout, login_status), library retrieval (get_library, get_library_ids, lookup_watched), title info (get_title, search, resolve_id), write actions (mark_watched, set_status, rate, remove_from_history), and sync support (get_activities, get_ratings). Even similar tools like get_library vs get_library_ids are explicitly differentiated by intent (full data vs ID-only for deletion reconciliation).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb-noun pattern (e.g., get_activities, mark_watched, resolve_id). Verbs are uniform across CRUD-like operations, and even standalone verbs like 'search' and 'rate' fit the pattern. No mixed conventions or ambiguous naming.

    Tool Count5/5

    14 tools is well-scoped for a media library sync and recommendation server. Each tool fills a clear role—auth, reading, writing, ID resolution, and search—without redundancy. The count is neither bloated nor insufficient, covering the full integration surface.

    Completeness5/5

    The tool surface covers the entire lifecycle: login status, library synchronization with delta support, deletion reconciliation, direct watched-check, ratings, title details, ID resolution, search, and all write operations (mark, status, rate, remove). No obvious gaps for the stated purpose of powering a recommendation system.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources