AniList MCP Server connects LLM clients to the AniList platform, providing comprehensive access to anime and manga data through the AniList API. Key features: - Search for anime, manga, characters, staff members, and studios - Retrieve detailed information about specific titles, characters, and production staff - Access user profiles and personal anime/manga lists with optional authentication - Advanced filtering options by genre, tags, and other media attributes - Dual transport support (HTTP and STDIO) for both local and cloud deployments - OAuth integration for accessing private user data and personalized lists

AniList MCP Server

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.

Features

Requirements

Local Installation (STDIO Transport)

1. Add this server to your mcp.json / claude_desktop_config.json:

{
  "mcpServers": {
    "anilist": {
      "command": "npx",
      "args": ["-y", "anilist-mcp"],
      "env": {
        "ANILIST_TOKEN": "your_api_token"
      }
    }
  }
}

You may remove the env object entirely, if you are not planning to use the AniList Token for operations that require login.

2. Restart your MCP client (e.g., Claude Desktop) 3. Use the tools to interact with AniList

Server Deployment (HTTP Transport)

Self-Hosting

pnpm run start:http

Cloud Deployment

You can deploy this MCP server to any cloud platform that supports Node.js server applications.

You can also deploy via MCP platforms like Smithery.

Configuration

Environment Variables (STDIO Transport and HTTP Transport server where host provides the config)

When using the STDIO transport or hosting the HTTP transport server, you can pass configuration via environment variables:

> [!CAUTION] > If you are hosting the HTTP transport server with token pre-configured, you should protect your endpoint and implement authentication before allowing users to access it. Otherwise, anyone can access your MCP server while using your AniList token.

HTTP Headers (HTTP Transport where user provides the config)

When using the HTTP transport, user can pass configuration via HTTP headers:

If the user provides the token in the header, while the server also has ANILIST_TOKEN set, the header value will take precedence.

Get an AniList API Token (Optional)

To get an API token, follow these steps:

1. Go to AniList settings. 2. Click on "Create New Client". 3. Use this URL as your client's "Redirect URL":

https://anilist.co/api/v2/oauth/pin

4. Click "Save" 5. Then go to https://anilist.co/api/v2/oauth/authorize?client_id={clientID}&response_type=token, replace the {clientID} with the client ID you get. It will ask you to log in and then provide you with the token to use. 6. Copy the generated token and use it in your .env file or environment variables.

Available Tools

Misc Tools

Activity Tools

List Tools

Media Tools

People Tools