Ani Mcp

What is Ani Mcp?

Ani Mcp is a smart MCP (Model Context Protocol) server for AniList that adds an intelligence layer beyond raw API calls. It builds a taste profile from your completed list to deliver personalized picks, compatibility comparisons, sequel alerts, watch order, session planning, and year-in-review summaries, plus standard search, list management, and social features. Suitable for any MCP-compatible client.

How to use Ani Mcp?

Install by adding to your MCP client config (e.g., claude_desktop_config.json) with the command npx -y ani-mcp and an optional ANILIST_USERNAME environment variable. Also available via Docker or building from source. For write operations and private lists, set ANILIST_TOKEN with an AniList OAuth token.

Key features of Ani Mcp

• Taste profiling from your completed list
• Personalized picks based on mood
• Compare taste compatibility between users
• Sequel alerts for finished shows
• Watch order for franchises
• Session planning with time budget

Use cases of Ani Mcp

• "What should I watch next?" – uses taste profile and planning list
• "I want something dark and psychological" – mood-filtered picks
• "What's good this season?" – ranks seasonal anime by taste
• "I have 90 minutes, what should I watch?" – time‑budgeted session planning
• "Any sequels airing for stuff I've finished?" – cross‑references completed list

FAQ from Ani Mcp

What does Ani Mcp do differently from other AniList integrations?

It adds an intelligence layer: taste profiling, personalized picks, compatibility scoring, sequel detection, watch order traversal, and session planning – not just 1:1 API mirroring.

What are the requirements to run Ani Mcp?

Node.js (via npx or Docker), an internet connection, and an optional AniList username. Write operations need an AniList OAuth token set in ANILIST_TOKEN.

Does Ani Mcp store my data?

No. It runs locally, sends requests only to the AniList API, stores nothing, and collects no analytics. See PRIVACY.md for details.

What transport does Ani Mcp use?

Default is stdio. Set MCP_TRANSPORT to http for HTTP Stream transport on port 3000 (configurable via MCP_PORT and MCP_HOST).

Is authentication required?

No. An AniList username is optional for defaults; call tools can pass it per‑call. A token is required only for write operations (e.g., adding to list, rating) and accessing private lists.