[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# AniList API and MCP server

> AniList has a full, free public GraphQL API but no official MCP server (checked 17 Oct 2026). The API covers searching titles, reading and saving list entries, activity, favourites, follows and the forum. It needs an OAuth app and a token you handle yourself, and its docs currently note a degraded limit of 30 requests per minute.

Anime and manga database and tracker: your lists with status, progress and scores, a social activity feed, favourites, reviews and a forum.

## What is the AniList API?

Cotlet's AniList API exposes 14 endpoints for your own AniList account: search anime and manga, get a title, list an anime or manga list, get profile and list statistics, list activity, list notifications, search forum threads, add or update a list entry, remove a list entry, favourite or unfavourite a title, post a text activity, reply to an activity, follow or unfollow a user and comment in a forum thread. The search_media endpoint returns search AniList titles by name, with optional filters. Each endpoint takes simple JSON inputs like type, cursor or username and works both as an operation of the anilist_read or anilist_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-22

AniList has a full, free public GraphQL API but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for AniList with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does AniList have an official API?

AniList has a full, free public GraphQL API but no official MCP server (checked 17 Oct 2026). The API covers searching titles, reading and saving list entries, activity, favourites, follows and the forum. It needs an OAuth app and a token you handle yourself, and its docs currently note a degraded limit of 30 requests per minute.

| Task | AniList official | Cotlet |
|---|---|---|
| Search anime and manga | Yes: GraphQL Media and Page queries, no login needed; you write the query | Yes |
| Read a list by status | Yes: Reading a private list needs the OAuth token of its owner | Yes |
| Add or update a list entry (status, progress, score, notes) | Yes: SaveMediaListEntry mutation, needs an OAuth token | Yes |
| Favourite or unfavourite a title | Yes: ToggleFavourite mutation | Yes |
| Read activity and notifications | Yes: Activity and Notification queries; notifications need a token | Yes |
| Post a text activity or reply to one | Yes: SaveTextActivity and SaveActivityReply mutations | Yes |
| Follow or unfollow a user | Yes: ToggleFollow mutation | Yes |
| Comment in a forum thread | Yes: SaveThreadComment mutation | Yes |

Sources: [AniList API Docs: Introduction](https://docs.anilist.co/guide/introduction), [AniList API Docs: Authentication](https://docs.anilist.co/guide/auth/), [AniList API Docs: Rate limiting](https://docs.anilist.co/guide/rate-limiting), [AniList API Docs: Mutations reference](https://docs.anilist.co/reference/mutation)

## For AI agents

```text
AniList has a full, free public GraphQL API but no official MCP server (checked 17 Oct 2026). The API covers searching titles, reading and saving list entries, activity, favourites, follows and the forum. It needs an OAuth app and a token you handle yourself, and its docs currently note a degraded limit of 30 requests per minute.
Cotlet provides a hosted MCP server and REST API for AniList: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=anilist, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    anilist_read, anilist_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/anilist, each operation at its own route, e.g. POST /api/v1/anilist/medias/{media_id}/list-entry/save
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_media, get_media, list_media_list, get_user_stats, list_activity, list_notifications, list_forum_threads, save_list_entry, delete_list_entry, toggle_favourite, post_activity, reply_to_activity, follow_user, post_thread_comment
Confirm      save_list_entry, delete_list_entry, post_activity, reply_to_activity, follow_user, post_thread_comment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/anilist-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=anilist, requests AniList in the Cotlet console and creates an API key there.
2. The user signs in to AniList once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables AniList for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted AniList server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source AniList MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to AniList in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get AniList only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no AniList login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following AniList's terms; Cotlet is not affiliated with AniList.
```

## What can an AI agent do in AniList?

Cotlet is best for AniList users who keep large lists and a social feed and want an agent to update and answer them without running or fixing a server.

- **[Update anime list progress and scores](https://cotlet.dev/integrations/anilist-api-mcp-server/update-anime-list-progress.md)** (runs: weekly): "On my AniList anime list, take everything in Currently watching that I tell you I finished: set it to Completed, set progress to the last episode, and score it from my notes below. Show me the changes before you save." → `list_media_list`, `search_media`, `save_list_entry`
- **[Triage AniList notifications and reply](https://cotlet.dev/integrations/anilist-api-mcp-server/triage-anilist-notifications.md)** (runs: daily): "Read my unread AniList notifications. Summarize likes and follows in one line, and for replies and mentions in my activity draft a short answer. Post the replies I approve." → `list_notifications`, `list_activity`, `reply_to_activity`
- **Find manga and anime to add to Planning** (runs: weekly): "Find five highly rated anime from last season in genres I score above 8 that are not on my list yet. Add them to Planning." → `get_user_stats`, `search_media`, `save_list_entry`
- **Clean up favourites and follows**: "Show my favourite anime, remove the ones I scored below 7, and favourite my ten highest-rated manga." → `list_media_list`, `toggle_favourite`
- **Post a season recap to your AniList activity** (runs: weekly): "Summarize what I completed this week in two sentences and post it as a text activity." → `list_media_list`, `post_activity`

## Can AniList automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a AniList connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to update anime list progress and scores, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/anilist/media-lists. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/anilist/media-lists with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to AniList.

### search_media

Search AniList titles by name, with optional filters. Access: read. REST: `GET /api/v1/anilist/medias/search`. MCP: `anilist_read → search_media`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Title to search for, in romaji, English or native. |
| `type` | string | no | ANIME or MANGA. Leave out to search both. |
| `season_year` | integer | no | Only titles from this season year. |
| `genre` | string | no | Only titles with this genre. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns up to 50 titles per page with ID, titles, format, episode or chapter count, season year and average score. The order is the best match first. A title already on your list also shows its list status.

Example response:

```json
{
  "items": [
    {
      "media_id": 154587,
      "title": "Frieren: Beyond Journey's End",
      "type": "ANIME",
      "format": "TV",
      "episodes": 28,
      "season_year": 2023,
      "average_score": 91,
      "on_list": "CURRENT"
    }
  ],
  "next_cursor": null
}
```

### get_media

Read one anime or manga with its details. Access: read. REST: `GET /api/v1/anilist/medias/{media_id}`. MCP: `anilist_read → get_media`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `media_id` | integer | yes | AniList media ID from search_media or list_media_list. |

Returns titles, format, release status, episode or chapter count, genres, tags, average score and popularity. If the title is on your list, it adds your status, progress and score. It changes nothing.

Example response:

```json
{
  "media_id": 154587,
  "title": "Frieren: Beyond Journey's End",
  "type": "ANIME",
  "status": "FINISHED",
  "episodes": 28,
  "genres": [
    "Adventure",
    "Drama",
    "Fantasy"
  ],
  "average_score": 91,
  "your_entry": {
    "status": "CURRENT",
    "progress": 24,
    "score": null
  }
}
```

### list_media_list

Read a user's list, optionally filtered by status. Access: read. REST: `GET /api/v1/anilist/media-lists`. MCP: `anilist_read → list_media_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | ANIME or MANGA. |
| `username` | string | no | AniList username. Defaults to the signed-in account. |
| `status` | string | no | CURRENT, PLANNING, COMPLETED, DROPPED, PAUSED or REPEATING. Leave out for all. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns entries with media ID, title, status, progress, score and the date of the last update. Your own private entries are included only for the signed-in account. Long lists come back in pages.

Example response:

```json
{
  "items": [
    {
      "media_id": 154587,
      "title": "Frieren: Beyond Journey's End",
      "status": "CURRENT",
      "progress": 24,
      "score": null,
      "updated_at": "2026-10-15"
    },
    {
      "media_id": 166873,
      "title": "Dungeon Meshi",
      "status": "CURRENT",
      "progress": 22,
      "score": null,
      "updated_at": "2026-10-12"
    }
  ],
  "next_cursor": null
}
```

### get_user_stats

Read a profile with the totals AniList shows for it. Access: read. REST: `GET /api/v1/anilist/user-stats`. MCP: `anilist_read → get_user_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `username` | string | no | AniList username. Defaults to the signed-in account. |

Returns the profile name, score format, counts of titles per status, and the genres you rate highest. Private entries are counted only for your own account. It changes nothing.

Example response:

```json
{
  "username": "yourname",
  "score_format": "POINT_10",
  "anime": {
    "completed": 212,
    "current": 4,
    "planning": 87
  },
  "manga": {
    "completed": 31,
    "current": 2,
    "planning": 40
  },
  "top_genres": [
    "Fantasy",
    "Drama"
  ]
}
```

### list_activity

Read activities from a user or from the people you follow. Access: read. REST: `GET /api/v1/anilist/activities`. MCP: `anilist_read → list_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `username` | string | no | Only activity from this user. Leave out for people you follow. |
| `type` | string | no | TEXT, ANIME_LIST, MANGA_LIST or MESSAGE. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns newest first, with activity ID, type, author, text or the list change, like count and replies. Messages are returned only when you are the sender or recipient. It changes nothing.

Example response:

```json
{
  "items": [
    {
      "activity_id": 912345678,
      "type": "TEXT",
      "author": "yourname",
      "text": "Episode 9 of Frieren hit hard.",
      "likes": 3,
      "replies": [
        {
          "author": "friend42",
          "text": "Same, the music!"
        }
      ]
    }
  ],
  "next_cursor": null
}
```

### list_notifications

Read your notifications, optionally by type. Access: read. REST: `GET /api/v1/anilist/notifications`. MCP: `anilist_read → list_notifications`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | no | One of ACTIVITY_REPLY, ACTIVITY_MENTION, ACTIVITY_MESSAGE, FOLLOWING, AIRING, ACTIVITY_LIKE, THREAD_COMMENT_MENTION. Leave out for all. |
| `mark_read` | boolean | no | Reset the unread count when reading. Defaults to false. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns newest first, with type, the user who caused it and the activity or thread it points to. The unread count resets only if mark_read is true. It changes nothing else.

Example response:

```json
{
  "unread": 14,
  "items": [
    {
      "type": "ACTIVITY_REPLY",
      "user": "friend42",
      "activity_id": 912345678,
      "text": "Same, the music!"
    },
    {
      "type": "FOLLOWING",
      "user": "newfan7"
    }
  ],
  "next_cursor": null
}
```

### list_forum_threads

Search AniList forum threads by words. Access: read. REST: `GET /api/v1/anilist/forum-threads`. MCP: `anilist_read → list_forum_threads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | yes | Words to look for in thread titles. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns thread ID, title, author, reply count and the date of the last reply, newest activity first. Use the ID with post_thread_comment. It changes nothing.

Example response:

```json
{
  "items": [
    {
      "thread_id": 31337,
      "title": "Frieren episode 28 discussion",
      "author": "friend42",
      "replies": 214,
      "last_reply": "2026-10-16"
    }
  ],
  "next_cursor": null
}
```

### save_list_entry

Create or change a list entry for an anime or manga. Access: write, asks the user first. REST: `POST /api/v1/anilist/medias/{media_id}/list-entry/save`. MCP: `anilist_write → save_list_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `media_id` | integer | yes | AniList media ID from search_media or list_media_list. |
| `status` | string | no | CURRENT, PLANNING, COMPLETED, DROPPED, PAUSED or REPEATING. |
| `progress` | integer | no | Episodes or chapters consumed. |
| `score` | number | no | Score in your account's scoring system, for example 0 to 10 for a 10-point scale. |
| `notes` | string | no | Your notes on the entry, up to 6000 characters. |
| `private` | boolean | no | Keep the entry visible only to you. |

Creates the entry if the title is not on your list, otherwise changes only the fields you send. Returns the saved entry. The change can show in your activity feed to people who follow you, unless the entry is private. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "entry_id": 481337021,
  "media": {
    "media_id": 154587,
    "title": "Frieren: Beyond Journey's End"
  },
  "status": "COMPLETED",
  "progress": 28,
  "score": 9,
  "private": false
}
```

### delete_list_entry

Delete an entry from your list. Access: write, asks the user first. REST: `DELETE /api/v1/anilist/entries/{entry_id}/list-entries`. MCP: `anilist_write → delete_list_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `entry_id` | integer | yes | Entry ID from list_media_list or save_list_entry. |

Removes the entry with its status, progress, score and notes. Adding the title again starts an empty entry, so the old values are not restored. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "entry_id": 481337021,
  "deleted": true
}
```

### toggle_favourite

Add a title to your favourites, or remove it if it is already there. Access: write. REST: `PUT /api/v1/anilist/medias/{media_id}/favourite`. MCP: `anilist_write → toggle_favourite`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | ANIME or MANGA. |
| `media_id` | integer | yes | AniList media ID from search_media or list_media_list. |

Returns whether the title is now a favourite. It reaches no one directly and one more call undoes it, so it does not ask for confirmation by default. Favourites are shown on your profile.

Example response:

```json
{
  "media_id": 154587,
  "favourite": true
}
```

### post_activity

Publish a text post to your AniList activity feed. Access: write, asks the user first. REST: `POST /api/v1/anilist/activities`. MCP: `anilist_write → post_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `text` | string | yes | Post text, 5 to 10000 characters. |

Publishes to your profile and shows to your followers. Returns the new activity ID and its link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "activity_id": 912345999,
  "url": "https://anilist.co/activity/912345999",
  "posted": true
}
```

### reply_to_activity

Reply to a text or list activity. Access: write, asks the user first. REST: `POST /api/v1/anilist/activities/{activity_id}/replies`. MCP: `anilist_write → reply_to_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | integer | yes | Activity ID from list_activity or list_notifications. |
| `text` | string | yes | Reply text, 2 to 8000 characters. |

Posts a public reply under the activity, and its author gets a notification. Returns the reply ID. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "reply_id": 77120045,
  "activity_id": 912345678,
  "posted": true
}
```

### follow_user

Follow a user, or unfollow if you already do. Access: write, asks the user first. REST: `POST /api/v1/anilist/user/follow`. MCP: `anilist_write → follow_user`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `username` | string | yes | AniList username. |

The other user gets a following notification. Returns whether you now follow them. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "username": "newfan7",
  "following": true
}
```

### post_thread_comment

Post a comment in a forum thread, or reply to a comment. Access: write, asks the user first. REST: `POST /api/v1/anilist/threads/{thread_id}/comment`. MCP: `anilist_write → post_thread_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `thread_id` | integer | yes | Thread ID from list_forum_threads. |
| `comment` | string | yes | Comment text in markdown, 1 to 12000 characters. |
| `parent_comment_id` | integer | no | Reply to this comment instead of the thread. |

Posts publicly in the thread and notifies people who subscribed to it. Returns the comment ID. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": 5550123,
  "thread_id": 31337,
  "posted": true
}
```

## How do I connect AniList to Claude Code, Codex or Cursor?

Connecting AniList takes three steps: sign up, sign in to AniList once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect AniList to your agent.

1. **Create an account** Sign up and add AniList in the console. Your API key is there too.

2. **Sign in to AniList in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to AniList there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the AniList tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
On my AniList anime list, take everything in Currently watching that I tell you I finished: set it to Completed, set progress to the last episode, and score it from my notes below. Show me the changes before you save.
```

### Call AniList from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/anilist with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/anilist/medias/154587/list-entry/save \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"COMPLETED","progress":28,"score":9}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "entry_id": 481337021,
  "media": {
    "media_id": 154587,
    "title": "Frieren: Beyond Journey's End"
  },
  "status": "COMPLETED",
  "progress": 28,
  "score": 9,
  "private": false
}
```

## Why use Cotlet for AniList?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to AniList yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When AniList changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect AniList to Cotlet?

Yes. You sign in to AniList yourself, in your own Cloud Browser, and we never save your password. Your agents only get AniList once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official AniList integration?**

No, Cotlet is independent of AniList. AniList's own API is too limited for this work. Cotlet works through your own AniList account, the way you use AniList in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to AniList in your console: your agents lose access at once and you stay signed in. Signing out of AniList in the browser works too, and Reset browser deletes the whole profile.

## Is there a AniList MCP server on GitHub?

Yes. Community AniList MCP servers exist on GitHub, usually maintained by one person. They run on the GraphQL API: you register an OAuth app, get a token, install the server on your own computer and keep it running yourself. When the API or the server changes, you or the maintainer fix it. Cotlet hosts the same kind of server for you, with no OAuth app to register, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Register an app in AniList developer settings, run the OAuth flow, install the server, add the token to each MCP client | Sign up, sign in to AniList once, add one MCP server or API key |
| When AniList changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your AniList access | An access token in a file on your computer; AniList tokens have no scopes and give almost full access to the account | A session in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | The token lasts 1 year and has no refresh; you authorize again by hand | Your Cloud Browser keeps you signed in; if AniList logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when AniList changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the AniList API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the AniList API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own AniList account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to AniList yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get AniList only after you enable it. When AniList signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to AniList, sign out of AniList in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **AniList's terms:** You use your own AniList account and stay responsible for following AniList's terms. Cotlet is independent and not affiliated with AniList. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open AniList in the console and press Request access. Then you create your API key and connect AniList there.

**Do I need to be technical?**

No. You sign in to AniList once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect AniList to Cotlet?**

Yes. You sign in to AniList yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get AniList once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My AniList sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your AniList cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through AniList's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. AniList sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no AniList login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

AniList offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Is the AniList API free?**

Yes for non-commercial use. AniList's terms allow commercial apps under $150 of revenue per month free of charge and ask larger ones to get a commercial license (checked 17 Oct 2026). The terms also forbid hoarding or mass collection of data, so use an agent for your own lists, not for scraping the catalog.

**What is the rate limit?**

The AniList docs state a limit of 90 requests per minute, with a note that the API is degraded and limited to 30 per minute for now. Pages hold at most 50 entries, so long lists take several calls.

**Can my agent post or send messages in AniList without asking me?**

No. Every call to save_list_entry, delete_list_entry, post_activity, reply_to_activity, follow_user or post_thread_comment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. toggle_favourite runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the AniList API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/anilist from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.