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
    123 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
    69 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.
    146 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
    B
    maintenance
    Enables searching and retrieving anime and manga data from MyAnimeList via the Jikan API, including anime details, top rankings, and character information.
    28 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

A4.1/5.0

Scored across 50 tools

Disambiguation4/5

Most tools map cleanly to a distinct resource+action, and the descriptions explicitly separate near neighbors like search_activity, get_user_activity, and get_user_recent_activity. A few overlapping clusters remain—add_list_entry upserts like update_list_entry, and get_studio's fuzzy name search overlaps search_studio—so an agent must read carefully but can usually pick correctly.

Naming Consistency5/5

All 50 names follow the same snake_case verb-first pattern (get_, search_, post_, update_, delete_, toggle_, add_, remove_) with clear resource nouns, from get_media and search_character to post_thread_comment and toggle_favourite. The use of remove for list entries instead of delete is a synonym, not a real pattern break.

Tool Count3/5

50 tools is a heavy surface, though the AniList domain is genuinely broad (media, people, studios, users, lists, activity, forums, auth). The count is inflated by convenience wrappers and near-duplicates such as get_full_user_info, get_user_recent_activity, and search_studio, so it feels larger than strictly necessary.

Completeness4/5

Core lifecycles are well covered: media search/read, list entry add/update/remove, activity and thread create/read/update/delete, plus auth and user settings. Obvious gaps are social mutations like liking posts/threads/comments and voting on recommendations (explicitly noted as unavailable), plus review creation, so agents have to work around those.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources