AniList MCP server for accessing AniList API data
If you want an AI assistant working directly with AniList, the anilist mcp server is the bridge. AniList MCP server for accessing AniList API data.
A Model Context Protocol (MCP) server that interfaces with the AniList API, allowing LLM clients to access and interact with anime, manga, character, staff, and user data from AniList.
Once connected, the assistant can call these 14 tools directly:
get_genres — Get all available genres on AniListget_media_tags — Get all available media tags on AniListget_site_statistics — Get AniList site statistics over the last seven daysget_studio — Get information about a studio by its AniList ID or namefavourite_studio — [Requires Login] Favourite or unfavourite a studio by its IDdelete_activity — [Requires Login] Delete the current authorized user's activity postget_activity — Get a specific AniList activity by its IDget_user_activity — Fetch activities from a userpost_message_activity — [Requires Login] Post a new message activity or update an existing onepost_text_activity — [Requires Login] Post a new text activity or update an existing oneget_user_anime_list — Get a user's anime listget_user_manga_list — Get a user's manga listadd_list_entry — [Requires Login] Add an entry to the authorized user's listremove_list_entry — [Requires Login] Remove an entry from the authorized user's listThe server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply one environment variable: ANILIST_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. AniList sits in that group, and the shape of its toolset — get_genres, get_media_tags, get_site_statistics among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| get_genres | Get all available genres on AniList |
| get_media_tags | Get all available media tags on AniList |
| get_site_statistics | Get AniList site statistics over the last seven days |
| get_studio | Get information about a studio by its AniList ID or name |
| favourite_studio | [Requires Login] Favourite or unfavourite a studio by its ID |
| delete_activity | [Requires Login] Delete the current authorized user's activity post |
| get_activity | Get a specific AniList activity by its ID |
| get_user_activity | Fetch activities from a user |
| post_message_activity | [Requires Login] Post a new message activity or update an existing one |
| post_text_activity | [Requires Login] Post a new text activity or update an existing one |
| get_user_anime_list | Get a user's anime list |
| get_user_manga_list | Get a user's manga list |
| add_list_entry | [Requires Login] Add an entry to the authorized user's list |
| remove_list_entry | [Requires Login] Remove an entry from the authorized user's list |
{
"mcpServers": {
"anilist": {
"command": "npx",
"args": ["-y", "anilist-mcp"],
"env": {
"ANILIST_TOKEN": "your_api_token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ANILIST_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.