[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)

# Habitica API and MCP server

> Habitica has a full public REST API (v3) but no official MCP server (checked 17 Oct 2026). The API reads and changes tasks, tags, pets, mounts, parties and quests. Third-party tools may make 30 requests per minute per user, and each request must carry an X-Client header with the tool author's user ID.

Habit tracker built as a role-playing game: habits, dailies and to-dos earn experience and gold, and missed dailies cost health. Players can join a party and fight quests together.

## What is the Habitica API?

Cotlet's Habitica API exposes 14 endpoints for your own Habitica account: list tasks, get a task, list tags, get party and quest, list pets, mounts and items, create a task, update a task, score a habit or tick a daily, add a checklist item, tick a checklist item, hatch a pet, feed a pet, accept a party quest invite and force-start the party quest. The list_tasks endpoint returns list your habits, dailies, to-dos or rewards. Each endpoint takes simple JSON inputs like task_id, text or type and works both as an operation of the habitica_read or habitica_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 14 (5 read, 9 write)
- **Updated:** 2026-10-19

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

## Does Habitica have an official API?

Habitica has a full public REST API (v3) but no official MCP server (checked 17 Oct 2026). The API reads and changes tasks, tags, pets, mounts, parties and quests. Third-party tools may make 30 requests per minute per user, and each request must carry an X-Client header with the tool author's user ID.

| Task | Habitica official | Cotlet |
|---|---|---|
| List tasks and read one with its checklist | Yes: REST API; you send your user ID and API token | Yes |
| Create habits, dailies and to-dos | Yes: REST API; no MCP server for agents | Yes |
| Score a habit or tick a daily | Yes: REST API | Yes |
| Add and tick checklist items | Yes: REST API | Yes |
| Hatch and feed pets | Yes: REST API | Yes |
| Read the party and its quest | Yes: REST API | Yes |
| Accept or force-start a party quest | Yes: REST API | Yes |
| Run all of the above from an agent with no token, header or rate limiter to manage | No: You write and run that layer yourself | Yes |

Sources: [Habitica GitHub wiki: API Usage Guidelines](https://github.com/HabitRPG/habitica/wiki/API-Usage-Guidelines), [Habitica API documentation](https://habitica.com/apidoc/), [Habitica Wiki: Application Programming Interface](https://habitica.fandom.com/wiki/Application_Programming_Interface), [Habitica Wiki: Guidance for Comrades](https://habitica.fandom.com/wiki/Guidance_for_Comrades)

## For AI agents

```text
Habitica has a full public REST API (v3) but no official MCP server (checked 17 Oct 2026). The API reads and changes tasks, tags, pets, mounts, parties and quests. Third-party tools may make 30 requests per minute per user, and each request must carry an X-Client header with the tool author's user ID.
Cotlet provides a hosted MCP server and REST API for Habitica: 14 tools (5 read, 9 write).
Access       Sign up at https://cotlet.dev/app/signup?app=habitica, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    habitica_read, habitica_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/habitica, each operation at its own route, e.g. POST /api/v1/habitica/tasks
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   list_tasks, get_task, list_tags, get_party, list_pets_and_mounts, create_task, update_task, score_task, add_checklist_item, tick_checklist_item, hatch_pet, feed_pet, accept_quest, start_quest
Confirm      hatch_pet, feed_pet, accept_quest, start_quest (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/habitica-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=habitica, requests Habitica in the Cotlet console and creates an API key there.
2. The user signs in to Habitica once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Habitica 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 Habitica 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 Habitica 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 Habitica 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 Habitica 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 Habitica 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 Habitica's terms; Cotlet is not affiliated with Habitica.
```

## What can an AI agent do in Habitica?

Cotlet is best for Habitica players and small parties who want an agent to add tasks, tick dailies and start quests without running or fixing a server.

- **[Create recurring tasks from a list](https://cotlet.dev/integrations/habitica-api-mcp-server/create-recurring-tasks-from-a-list.md)**: "Add these as Habitica dailies: stretch 10 minutes, review inbox, water the plants. Make "water the plants" due only on Sundays. Set stretch to easy and skip any that already exist." → `list_tasks`, `create_task`
- **[Check off done dailies each evening](https://cotlet.dev/integrations/habitica-api-mcp-server/check-off-done-dailies.md)** (runs: daily): "Look at my Habitica dailies due today. From my notes below, tick the ones I did. List the ones I did not mention and leave them unticked." → `list_tasks`, `score_task`
- **[Start the party quest on a schedule](https://cotlet.dev/integrations/habitica-api-mcp-server/start-party-quest-on-schedule.md)**: "Check my Habitica party quest. If it is still pending and some members have not answered, force-start it at 18:00 on Friday and tell me who was left out." → `get_party`, `start_quest`
- **Break a to-do into a checklist**: "Take my Habitica to-do "Move apartment" and split it into a checklist of concrete steps. Do not remove anything already on it." → `list_tasks`, `get_task`, `add_checklist_item`
- **Hatch and feed pets with spare items** (runs: weekly): "List my Habitica eggs, hatching potions and food. Hatch every egg that has a potion, and tell me which pets could be fed." → `list_pets_and_mounts`, `hatch_pet`, `feed_pet`

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

Yes. Cotlet does not replace your automation platform: it gives it a Habitica 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 check off done dailies each evening, 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/habitica/tasks. | 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/habitica/tasks 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 Habitica.

### list_tasks

List your habits, dailies, to-dos or rewards. Access: read. REST: `GET /api/v1/habitica/tasks`. MCP: `habitica_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | no | One of: habit, daily, todo or reward. Omit for habits, dailies and to-dos. |
| `tag` | string | no | Only tasks with this tag name. |

Returns each task with its ID, type, title, notes, difficulty, tags and, for dailies, whether it is due today and its streak. Checklist items are included. Tasks come in the order Habitica shows them.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "b7c1f6a0-3d52-4e1a-9a7e-5d1c0f2e8a11",
      "type": "daily",
      "title": "Stretch 10 minutes",
      "difficulty": "easy",
      "due_today": true,
      "completed": false,
      "streak": 12,
      "tags": [
        "morning"
      ]
    }
  ]
}
```

### get_task

Read one task with its notes and checklist. Access: read. REST: `GET /api/v1/habitica/tasks/{task_id}`. MCP: `habitica_read → get_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_tasks. |

Returns the title, notes, difficulty, tags, repeat settings for a daily or due date for a to-do, and every checklist item with its ID and state. Use it before editing a checklist.

Example response:

```json
{
  "task_id": "4e0b9c12-77a3-4d0f-8b1e-2a6f9d3c5e70",
  "type": "todo",
  "title": "Move apartment",
  "difficulty": "hard",
  "due": "2026-11-15",
  "checklist": [
    {
      "item_id": "c1",
      "text": "Book the movers",
      "done": true
    },
    {
      "item_id": "c2",
      "text": "Cancel electricity",
      "done": false
    }
  ]
}
```

### list_tags

List the tags on your account. Access: read. REST: `GET /api/v1/habitica/tags`. MCP: `habitica_read → list_tags`.

No parameters.

Returns each tag with its ID and name. Use the names with list_tasks and create_task.

Example response:

```json
{
  "tags": [
    {
      "tag_id": "a31d",
      "name": "morning"
    },
    {
      "tag_id": "f90e",
      "name": "home"
    }
  ]
}
```

### get_party

Read your party, its members and the current quest. Access: read. REST: `GET /api/v1/habitica/party`. MCP: `habitica_read → get_party`.

No parameters.

Returns the party name, its members and, if a quest is running or pending, the quest name and whether each member has accepted, rejected or not answered. Returns no quest block when your party has none. Works only if you are in a party.

Example response:

```json
{
  "party": "Morning Club",
  "members": 5,
  "quest": {
    "name": "The Dilatory Distraction",
    "state": "pending",
    "owner": "Anna",
    "answers": {
      "accepted": 3,
      "rejected": 0,
      "pending": 2
    }
  }
}
```

### list_pets_and_mounts

List your pets, mounts, eggs, hatching potions and food. Access: read. REST: `GET /api/v1/habitica/pets-and-mounts`. MCP: `habitica_read → list_pets_and_mounts`.

No parameters.

Returns the pets and mounts you own and the eggs, hatching potions and food in your inventory with counts. Pets that can still be fed are marked. Nothing is changed.

Example response:

```json
{
  "eggs": {
    "Wolf": 2,
    "Fox": 1
  },
  "hatching_potions": {
    "Base": 1,
    "Red": 1
  },
  "food": {
    "Meat": 3
  },
  "pets": [
    "Wolf-Base"
  ],
  "mounts": []
}
```

### create_task

Add a habit, daily, to-do or reward. Access: write. REST: `POST /api/v1/habitica/tasks`. MCP: `habitica_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | One of: habit, daily, todo or reward. |
| `text` | string | yes | Task title. |
| `notes` | string | no | Longer notes. |
| `difficulty` | string | no | One of: trivial, easy, medium, hard. |
| `repeat_days` | string[] | no | For a daily: the days it is due. One or more of: mo, tu, we, th, fr, sa, su. |
| `due` | string | no | For a to-do: due date, ISO. |
| `tags` | string[] | no | Tag names from list_tags. |

Creates the task in your own account and returns its ID. It reaches no one and you can delete it in Habitica, so it does not ask for OK by default. A daily without repeat_days is due every day.

Example response:

```json
{
  "task_id": "9d2a7e44-1c6b-4f58-a0e3-7b8c1d2f3a55",
  "type": "daily",
  "title": "Water the plants",
  "difficulty": "easy",
  "repeat_days": [
    "su"
  ]
}
```

### update_task

Change a task's title, notes, difficulty, due days or tags. Access: write. REST: `PATCH /api/v1/habitica/tasks/{task_id}`. MCP: `habitica_write → update_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_tasks. |
| `text` | string | no | New title. |
| `notes` | string | no | New notes. |
| `difficulty` | string | no | One of: trivial, easy, medium, hard. |
| `repeat_days` | string[] | no | For a daily: the days it is due. One or more of: mo, tu, we, th, fr, sa, su. |

Changes only the fields you send and returns the task as it is now. It reaches no one and a second call puts the old values back, so it does not ask for OK by default.

Example response:

```json
{
  "task_id": "b7c1f6a0-3d52-4e1a-9a7e-5d1c0f2e8a11",
  "title": "Stretch 15 minutes",
  "difficulty": "easy"
}
```

### score_task

Tick a daily or to-do, or score a habit up or down. Access: write. REST: `POST /api/v1/habitica/tasks/{task_id}/score`. MCP: `habitica_write → score_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_tasks. |
| `direction` | string | yes | One of: up, down. A daily or to-do uses up to tick it and down to untick it. |

Applies the same result as clicking the task in Habitica and returns the new streak or completion state. Scoring up on a habit counts toward your rewards. It changes only your own account and a second call reverses it, so it does not ask for OK by default.

Example response:

```json
{
  "task_id": "b7c1f6a0-3d52-4e1a-9a7e-5d1c0f2e8a11",
  "direction": "up",
  "completed": true,
  "streak": 13
}
```

### add_checklist_item

Add one item to a task's checklist. Access: write. REST: `POST /api/v1/habitica/tasks/{task_id}/checklist-items`. MCP: `habitica_write → add_checklist_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_tasks. |
| `text` | string | yes | Checklist item text. |

Appends the item to the end of the checklist and returns the full checklist. It changes only your own task and you can delete the item in Habitica, so it does not ask for OK by default.

Example response:

```json
{
  "task_id": "4e0b9c12-77a3-4d0f-8b1e-2a6f9d3c5e70",
  "checklist": [
    {
      "item_id": "c1",
      "text": "Book the movers",
      "done": true
    },
    {
      "item_id": "c2",
      "text": "Cancel electricity",
      "done": false
    },
    {
      "item_id": "c3",
      "text": "Pack the kitchen",
      "done": false
    }
  ]
}
```

### tick_checklist_item

Tick or untick one checklist item. Access: write. REST: `POST /api/v1/habitica/tasks/{task_id}/checklist-item/tick`. MCP: `habitica_write → tick_checklist_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_tasks. |
| `item_id` | string | yes | Checklist item ID from get_task. |

Flips the item between done and not done and returns the checklist. It changes only your own task and a second call undoes it, so it does not ask for OK by default.

Example response:

```json
{
  "task_id": "4e0b9c12-77a3-4d0f-8b1e-2a6f9d3c5e70",
  "item_id": "c2",
  "done": true
}
```

### hatch_pet

Hatch a pet from an egg and a hatching potion. Access: write, asks the user first. REST: `POST /api/v1/habitica/pet/hatch`. MCP: `habitica_write → hatch_pet`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `egg` | string | yes | Egg name from list_pets_and_mounts, for example Wolf. |
| `hatching_potion` | string | yes | Potion name from list_pets_and_mounts, for example Base. |

Uses one egg and one potion and returns the new pet. A potion that does not fit the egg changes nothing and the call returns an error. It uses up the items, so check the pair first.

Example response:

```json
{
  "pet": "Wolf-Base",
  "eggs_left": {
    "Wolf": 1,
    "Fox": 1
  },
  "hatching_potions_left": {
    "Red": 1
  }
}
```

### feed_pet

Feed a pet one food item. Access: write, asks the user first. REST: `POST /api/v1/habitica/pet/feed`. MCP: `habitica_write → feed_pet`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pet` | string | yes | Pet name from list_pets_and_mounts, for example Wolf-Base. |
| `food` | string | yes | Food name from list_pets_and_mounts, for example Meat. |

Uses one food item on the pet and returns how fed it is. Pets have food preferences, so some food is wasted on the wrong pet. A fed pet can become a mount.

Example response:

```json
{
  "pet": "Wolf-Base",
  "food": "Meat",
  "food_left": {
    "Meat": 2
  }
}
```

### accept_quest

Accept the pending quest invite for your party. Access: write, asks the user first. REST: `POST /api/v1/habitica/quest/accept`. MCP: `habitica_write → accept_quest`.

No parameters.

Joins you to the quest your party was invited to and returns the quest state. The other members see that you accepted. Works only while an invite is pending.

Example response:

```json
{
  "quest": "The Dilatory Distraction",
  "you": "accepted",
  "accepted": 4,
  "pending": 1
}
```

### start_quest

Start the pending quest without waiting for every answer. Access: write, asks the user first. REST: `POST /api/v1/habitica/quest/start`. MCP: `habitica_write → start_quest`.

No parameters.

Begins the quest with the members who accepted and returns the quest state. Only the quest owner or the party leader can call it. The members who have not answered are left out. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quest": "The Dilatory Distraction",
  "state": "active",
  "members_in": 3,
  "members_out": [
    "Mira",
    "Tomek"
  ]
}
```

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

Connecting Habitica takes three steps: sign up, sign in to Habitica 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 Habitica to your agent.

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

2. **Sign in to Habitica in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Habitica 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 Habitica 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.

```
Add these as Habitica dailies: stretch 10 minutes, review inbox, water the plants. Make "water the plants" due only on Sundays. Set stretch to easy and skip any that already exist.
```

### Call Habitica 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/habitica 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/habitica/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"daily","text":"Water the plants","difficulty":"easy","repeat_days":["su"]}'
```

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

```
{
  "task_id": "9d2a7e44-1c6b-4f58-a0e3-7b8c1d2f3a55",
  "type": "daily",
  "title": "Water the plants",
  "difficulty": "easy",
  "repeat_days": [
    "su"
  ]
}
```

## Why use Cotlet for Habitica?

**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 Habitica 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 Habitica changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Habitica to Cotlet?

Yes. You sign in to Habitica yourself, in your own Cloud Browser, and we never save your password. Your agents only get Habitica 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 Habitica integration?**

No, Cotlet is independent of Habitica. Habitica's own API is too limited for this work. Cotlet works through your own Habitica account, the way you use Habitica 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 Habitica in your console: your agents lose access at once and you stay signed in. Signing out of Habitica in the browser works too, and Reset browser deletes the whole profile.

## Is there a Habitica MCP server on GitHub?

Yes. Open-source Habitica MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it your user ID and API token, and fix it when Habitica changes. Cotlet hosts the same kind of server for you, works in your signed-in session, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, copy your user ID and API token from Habitica settings, add the server to each MCP client | Sign up, sign in to Habitica once, add one MCP server or API key |
| When Habitica changes | It breaks until you or the maintainer fix it; the X-Client header rule broke older tools in July 2025 | Our team tests it daily and fixes it for you; failed calls are free |
| Your Habitica access | User ID and API token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, session encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you paste a new token | Your Cloud Browser keeps you signed in; if Habitica logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself, and keep to the 30 requests per minute 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 Habitica 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 Habitica API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Habitica 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 Habitica 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 Habitica 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 Habitica only after you enable it. When Habitica 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 Habitica, sign out of Habitica 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.
- **Habitica's terms:** You use your own Habitica account and stay responsible for following Habitica's terms. Cotlet is independent and not affiliated with Habitica. [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 Habitica in the console and press Request access. Then you create your API key and connect Habitica there.

**Do I need to be technical?**

No. You sign in to Habitica 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 Habitica to Cotlet?**

Yes. You sign in to Habitica yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Habitica 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 Habitica 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 Habitica 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 Habitica's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Habitica 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 Habitica 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?**

Habitica 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).

**Does Habitica limit how fast an agent can call it?**

Yes. Third-party tools may make 30 requests per minute per user, and that limit is shared by every third-party tool on your account (checked 17 Oct 2026). Over the limit Habitica answers 429 with a Retry-After header. Long jobs, such as a list of fifty tasks, take a few minutes.

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

No. Every call to hatch_pet, feed_pet, accept_quest or start_quest waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_task, update_task, score_task, add_checklist_item, tick_checklist_item runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Habitica 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/habitica 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.