Summary
Writing GraphQL against AniList's schema for a question you will ask once.
Each question is its own tool rather than a query builder, so a season lookup, a voice-actor credit and a user's statistics are one call each with no field selection to get right. The tools that change anything — list entries, favourites, activity posts, follows, account settings — carry a [Requires Login] marker in their own description, which is a useful line to read before granting the token.
What it is
An AniList client with 44 tools: search and detail lookups across anime, manga, characters, staff, studios, threads and users, plus the authorized write side for lists, favourites and activity.
What you get
- Search across anime, manga, characters, staff, studios, users and activities, each with paging and filters
- Detail lookups by AniList ID — media, character, staff and studio — with a fullData switch on anime and manga
- Recommendations, both a specific recommendation by ID and the recommendation set for a given media
- A user's complete profile, statistics, recent activity and their anime and manga lists
- List entries added, updated and removed on the authorized account, and anime, manga, character, staff and studio favourites toggled
- Text and message activity posted, updated or deleted, plus following a user and updating account settings
- The reference data behind AniList's filters: every genre, every media tag, seven-day site statistics, and the characters and staff whose birthday is today
Requirements
Npx on your PATH, and ANILIST_TOKEN for the tools marked [Requires Login].
Setup effort
One command — npx -y anilist-mcp