Skip to main content
Glama
rollecode

Trakt MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Trakt MCP server

No user-submitted related servers found.

    Related Servers

    • simkl-mcp

      umsachde
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to read Simkl watch history, log watched items, manage library status, and search titles.
      14
      MIT

    • Plex MCP server

      rollecode
      A
      license
      C
      quality
      B
      maintenance
      Enables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.
      405
      12 npm
      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

    • Trakt MCP Server

      Lorenzo0111
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI agents to interact with Trakt.tv, including search, movies, TV shows, and user account features like watchlist and history.
      -

    • seerr-mcp

      rollecode
      A
      license
      B
      quality
      A
      maintenance
      Enables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.
      170
      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

    C2.5/5.0

    Scored across 338 tools

    Disambiguation1/5

    With 338 tools, many are near-duplicates differing only by path context (e.g., get_users_by_id_lists_by_list_id_items_movie vs get_lists_by_id_items_movie, list_certifications_movies vs get_certifications_by_type). The minimal descriptions ('Get items on a list') repeat across variants, making it nearly impossible to select the correct tool confidently.

    Naming Consistency2/5

    Names follow a path-derived snake_case pattern, but the verb prefix is inconsistent (get_ vs list_ for similar retrieval operations) and many names are malformed or awkward (e.g., get_users_by_id_lists_by_list_id_items_by_type_by_sort_by_by_sort_how contains 'by_by'). The pattern is not predictable enough to aid an agent.

    Tool Count1/5

    338 tools is an extreme over-exposure of the API surface. Even for a comprehensive API like Trakt, this is far beyond the manageable range and would overwhelm any agent. The scope should be split into multiple focused servers or drastically curated.

    Completeness4/5

    The tool set covers a remarkably broad portion of the Trakt API, including CRUD for lists, comments, sync, users, media metadata, search, calendars, and more. Most resources have corresponding get/create/update/delete operations, so obvious dead ends are rare.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources