Anilist logo

Anilist

Search, inspect, and browse trending anime through AniList’s GraphQL API with no authentication.

Install Anilist

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "anilist": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-anilist"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Anilist MCP server exposes AniList’s GraphQL API through MCP tools for anime search, detailed lookups, and trending titles. It can connect through the Pipeworx gateway over a remote MCP URL or run locally as a stdio server with npx. Use it when an agent needs structured anime metadata without AniList authentication. The gateway endpoint also includes shared Pipeworx meta-tools, while the standalone package provides only the three AniList tools.

Use cases

  • Search anime by title
  • Retrieve detailed anime metadata by ID
  • Check currently trending anime
  • Enrich search results with full season and studio information

Key features

  • Title-based anime search
  • Detailed anime lookup by AniList ID
  • Popularity-ranked trending anime
  • AniList GraphQL API access
  • Remote gateway and local stdio modes
  • No AniList authentication required

Tools3

What Anilist lets your agent do. Expand a tool for its parameters.

Verified live~249 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 33d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age184 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-anilist (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads385Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Anilist works

What the Anilist MCP server does

The Anilist MCP server gives MCP-compatible agents access to selected AniList GraphQL data. It focuses on anime discovery and reference rather than account actions or list management. No AniList authentication is required.

Three domain tools are available:

  • search_anime finds titles by name and returns basic fields such as episode count, release status, score, genres, and synopsis.
  • get_anime retrieves fuller information for a specific AniList ID, including synopsis, episode count, duration, status, score, genres, studios, and season details.
  • trending_anime returns currently trending anime ranked by popularity, with title, status, score, episode count, and genres.

Search and trending results include an ID that can be passed to get_anime for more complete information.

How it works

The Anilist MCP server can be used in two ways. A remote connection points an MCP client at https://gateway.pipeworx.io/anilist/mcp. That endpoint serves the AniList tools alongside shared Pipeworx gateway tools, including routing and discovery tools. The exact tool scope is reported by the connection’s initialize response and may change.

A local installation runs the package with npx -y @pipeworx/mcp-anilist. It communicates over standard input and output and exposes only the AniList tool set. Both modes use the same underlying source and provide the same three anime capabilities; the gateway mode adds Pipeworx-wide tools and routing.

The tools can also be called over HTTP through the gateway. For example, the gateway exposes the search operation at /v1/tools/anilist_search_anime and accepts a JSON request containing a query value.

Setup and configuration

For a remote MCP setup, add the gateway URL as an MCP server in a compatible client:

config.json
{
  "mcpServers": {
    "anilist": {
      "url": "https://gateway.pipeworx.io/anilist/mcp"
    }
  }
}

For local stdio use, configure the client to launch:

config.json
{
  "mcpServers": {
    "anilist": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-anilist"]
    }
  }
}

The provided setup requires no environment variables and no account for the initial calls. The package can be started directly with the same npx command to verify that it launches.

Tools and capabilities

The Anilist MCP server is suitable for agents that need to answer questions such as which anime match a title query, what details belong to a known anime ID, or which shows are currently trending. A typical workflow searches by title, selects an ID, and requests full details. Trending results follow the same pattern when additional metadata is needed.

The data fields are informational metadata supplied through the AniList GraphQL API. The documented tools do not expose user authentication, personal lists, mutations, or general GraphQL query construction.

Limitations and notes

This is an independent, unofficial integration and is not affiliated with, endorsed by, or published by AniList. The gateway pack endpoint includes additional shared Pipeworx schemas, so its reported tool count is larger than the three tools listed here. Use the local stdio package if only the AniList tools are wanted without gateway meta-tools or ask_pipeworx routing.

The project is licensed under MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Anilist

Anilist is an MCP server that connects AI agents to the AniList GraphQL API without authentication. Its main tools search anime by title, retrieve full anime details by AniList ID, and list currently trending anime with metadata such as scores, genres, episode counts, and status.

Install it as a local stdio server with npx using `npx -y @pipeworx/mcp-anilist`. Add that command and package argument to your MCP client configuration, or use the remote gateway URL at `https://gateway.pipeworx.io/anilist/mcp`.

Yes, Anilist works with Cursor through the remote MCP gateway configuration. Add `https://gateway.pipeworx.io/anilist/mcp` as the server URL; the README also names Claude Desktop and Windsurf as compatible setup targets.

Yes, you can run the package locally without a Pipeworx account by launching `@pipeworx/mcp-anilist` with npx. The local stdio mode avoids the gateway and exposes only the three AniList tools.

It provides `search_anime`, `get_anime`, and `trending_anime`. Search finds anime by title, get retrieves detailed data by ID, and trending returns currently popular anime; search and trending results can be followed with a full lookup.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAnilist AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/anilist?style=directory)](https://allmcps.com/mcp/anilist)
HTML Embed
<a href="https://allmcps.com/mcp/anilist"><img src="https://allmcps.com/api/badge/anilist?style=directory" alt="Anilist on AllMCPs" /></a>