Ani Mcp
Let your agent query AniList with taste-aware helpers—not raw API boilerplate—for lists, stats, and personalized anime/manga context in side projects or content tools.
Overview
ani-mcp is a MCP server for the Build phase that connects agents to AniList with taste-oriented list and stats tools over stdio.
What is this MCP server?
- Smart AniList MCP—emphasis on taste and context, not generic API passthrough
- npm ani-mcp stdio (v0.1.1); ANILIST_USERNAME default for lists and stats
- Optional ANILIST_TOKEN (OAuth) for authenticated queries
- Fits agent-driven rec engines, trackers, or community/content side builds
- Package ani-mcp version 0.1.1
- stdio transport
- 2 documented environment variables (username + optional secret token)
Community signal: 1 GitHub stars.
What problem does it solve?
Building an anime-aware agent feature means repeating AniList auth and queries instead of speaking in terms of user taste and lists.
Who is it for?
Indie devs building AniList-powered agents, trackers, or content assistants in Claude Code or Cursor.
Skip if: Teams with no AniList dependency or products that need unrelated CRM or payment MCPs.
What do I get? / Deliverables
After configuring username and optional token, your agent can pull AniList lists and stats through MCP tools tuned for personalization workflows.
- Agent-callable AniList list and stats operations
- Personalized context grounded in configured username
- Authenticated queries when token is supplied
Recommended MCP Servers
Journey fit
Third-party API MCP servers are classic build-phase integrations when you embed external data into an app, bot, or content workflow. AniList connectivity lives under integrations: optional ANILIST_USERNAME and ANILIST_TOKEN power list and stats tools beyond dumb REST wrappers.
How it compares
Domain-specific AniList MCP—not a general database or LLM gateway server.
Common Questions / FAQ
Who is ani-mcp for?
Builders and hobbyists who want their coding agent to use AniList lists and stats with a taste-aware MCP layer for apps or content tools.
When should I use ani-mcp?
Use it during build when you integrate AniList data into an agent feature and want default username-scoped tools plus optional OAuth.
How do I add ani-mcp to my agent?
Add the ani-mcp npm stdio server to MCP settings, set ANILIST_USERNAME and optionally ANILIST_TOKEN, then invoke list and stats tools from your host.