anilist-mcp
Related Servers
Alternatives to anilist-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP Server for interacting with the MyAnimeList API, allowing LLM clients to access and interact with anime, manga and more.152MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes MyAnimeList v2 API with OAuth authentication, enabling anime and manga search, rankings, seasonal charts, and user list management through natural language.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for MyAnimeList that enables searching anime/manga, getting details, rankings, seasons, characters, reviews, and user profiles without authentication, and managing personal anime/manga lists with authentication (token required).5476 npm2MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server for anime and manga discovery, enabling search, detail retrieval, franchise watch order, seasonal schedule, character lookups, rankings, and studio filmography via natural language.78 npm1Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for Anime News Network, enabling search of anime and manga encyclopedia entries, retrieval of details like cast, staff, and episodes, and access to news feeds. No API key or configuration required.473 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides access to MyAnimeList's API for anime and manga data. It enables users to search, view rankings, manage their personal lists, and get recommendations through Claude and other MCP clients.76 npm1MIT
TDQS
Scored across 44 tools
Most tools have distinct purposes targeting specific resources like anime, manga, characters, or user actions, with clear boundaries. However, some overlap exists between 'get_user_activity' and 'get_user_recent_activity', which could cause minor confusion about their exact scope.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'get_anime', 'search_character', and 'update_list_entry'. All tools use snake_case uniformly, making them predictable and easy to parse.
With 44 tools, the count is excessive for an AniList API server, leading to potential cognitive overload and redundancy. A more focused set of 10-20 tools could cover the same domain without overwhelming users or agents.
The tool set provides comprehensive coverage of the AniList domain, including CRUD operations for lists, favorites, and user activities, along with extensive search and retrieval functions for media, characters, staff, and more. No obvious gaps are present for core workflows.