Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to AniList MCP Server

  • ani-mcp

    gavxm
    A
    license
    A
    quality
    C
    maintenance
    A smart AniList integration for the Model Context Protocol that provides AI assistants with tools for searching media, managing watchlists, and analyzing user anime or manga tastes. It goes beyond basic API calls by offering personalized recommendations, taste comparisons, and natural language profile summaries.
    55
    53 npm
    3
    MIT

  • MAL MCP Server

    Grinv
    A
    license
    A
    quality
    A
    maintenance
    MCP 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).
    54
    102 npm
    3
    MIT

Related Servers

  • AniList MCP

    JunnB
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables interacting with AniList through natural language: searching anime, updating watch progress and scores, and surfacing currently airing episodes from your followed series.
    117 npm
    MIT

  • bangumi-mcp

    roxy-plugins
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables querying and updating Bangumi anime collections, tracking per-episode progress, and receiving airing reminders for currently-watching anime via AniList.
    -

  • mcp-jikan

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and retrieving anime and manga data from MyAnimeList via the Jikan API, including anime details, top rankings, and character information.
    2 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.9/5.0

Scored across 49 tools

Disambiguation3/5

Most tools target distinct resources, but several clusters overlap: get_user_activity/get_user_recent_activity/search_activity, get_user_profile/get_user_stats/get_full_user_info, and get_studio/search_studio all have fuzzy or redundant boundaries. The descriptions are unusually detailed and mitigate confusion, but an agent still faces real selection ambiguity across these near-overlapping tools.

Naming Consistency4/5

The overall verb_noun pattern is strong: get_*, search_*, post_*, delete_*, update_* cover most tools, with search_* and get_media_* subgroups consistent. Minor deviations like remove_list_entry vs delete_activity, login_anilist/submit_anilist_redirect, and add_list_entry vs create_* prevent a perfect score.

Tool Count2/5

49 tools is well above the 25+ threshold and feels heavy even for a broad anime/manga API. Some tools are redundant or consolidating (get_full_user_info duplicates get_user_profile + get_user_stats, get_user_recent_activity is a fixed subset of get_user_activity, get_studio overlaps search_studio), so the surface could be meaningfully trimmed.

Completeness4/5

The toolset covers the core AniList domain well: media search/detail, characters, staff, studios, list-entry CRUD, activities, threads, user profiles/stats, notifications, auth, and social toggles. Minor gaps exist—no like or recommendation-voting tools, no follower/following list retrieval, and no notification read/clear—but agents can work around these without dead-ending.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources