
Wraps the AniList GraphQL API so you can query anime and manga data without dealing with authentication or manual GraphQL calls. Part of the Pipeworx gateway, which offers a streamable HTTP transport and an ask_pipeworx tool that lets you make plain English requests instead of structured API calls. Free to use, no API key required. Useful when you're building features around anime recommendations, tracking watch lists, or pulling metadata for media collections. The gateway approach means you can either connect to this specific AniList wrapper or tap into the full Pipeworx network for 673+ data sources through a single configuration entry.
AniList MCP — wraps AniList GraphQL API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_anime | Search for anime by title. Returns title, episode count, status, score, genres, and synopsis. Use get_anime with the ID for full details. |
get_anime | Get full anime details by ID. Returns title, synopsis, episodes, duration, status, score, genres, studios, and season information. |
trending_anime | Get currently trending anime ranked by popularity. Returns title, status, score, episode count, and genres. Use get_anime with the ID for full details. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"anilist": {
"url": "https://gateway.pipeworx.io/anilist/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/anilist/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Anilist data" })
The gateway picks the right tool and fills the arguments automatically.
MIT