habitica-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HABITICA_USER_ID | Yes | Your Habitica User ID (required to call Habitica) | |
| HABITICA_BASE_URL | No | Another Habitica instance (self-hosted or a test double) | https://habitica.com |
| HABITICA_MCP_MODE | No | Set to `read-only` to expose only the four read tools | standard |
| HABITICA_X_CLIENT | No | Override the `x-client` header (for forks) | <maintainer id>-habitica-mcp |
| HABITICA_API_TOKEN | Yes | Your Habitica API Token (required, never logged) | |
| HABITICA_MCP_TIMEOUT | No | Request timeout in seconds | 20 |
| HABITICA_MCP_MAX_WAIT | No | Seconds to wait for a free request slot before failing fast | 10 |
| HABITICA_MCP_CACHE_TTL | No | Seconds reads are reused between tool calls (`0` disables) | 15 |
| HABITICA_MCP_LOG_LEVEL | No | Logs go to stderr; `INFO` adds one metrics line per tool call | WARNING |
| HABITICA_MCP_RATE_LIMIT | No | Max Habitica requests per minute (Habitica allows 30) | 25 |
| HABITICA_MCP_METRICS_FILE | No | Append per-call metrics (no task content) as JSON lines |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| habitica_get_overviewA | Snapshot of the user's Habitica day: character stats (HP, mana, XP, gold, level), dailies still due today, overdue / due-today / upcoming to-dos and habits, plus warnings such as a new day that has not started yet. Start here when the user asks what is pending or how they are doing. |
| habitica_list_tasksA | List the user's tasks with filters. Prefer filters over listing everything; returned ids can be passed to the other habitica_* tools. |
| habitica_get_taskA | Full details of one task: notes, checklist items with ids, schedule, tags and dates. |
| habitica_create_taskC | Create a habit, daily, to-do or reward. Tags are given by name. |
| habitica_update_taskA | Change fields of a task; only the given fields change. To check tasks off use habitica_score_task, and habitica_manage_checklist for checklist items. |
| habitica_score_taskA | Record progress: check off or undo a daily or to-do, press + or - on a habit, or buy a custom reward. Returns the character's stats after scoring and what changed. |
| habitica_delete_taskA | Permanently delete a task. Without confirm=true it only returns a preview: show it to the user and delete only after they agree. |
| habitica_manage_checklistA | Add, rename, check/uncheck or remove checklist items of a daily or to-do. Returns the task with its checklist item ids. |
| habitica_list_tagsA | List the user's tags with how many active tasks use each one. |
| habitica_manage_tagsA | Create, rename or delete a tag. To tag tasks use habitica_update_task(add_tags=...). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: overview vs. filtered listing, single-task detail, task CRUD, scoring, checklist management, and tag management are all separated. The potentially overlapping update_task vs. score_task boundary is explicitly clarified in the descriptions.
All tool names use a consistent habitica_ prefix followed by snake_case verb_noun patterns such as get_task, create_task, update_task, and list_tags. The manage_* tools are slightly aggregate but still follow the same predictable convention.
Ten tools is a well-scoped surface for Habitica task, scoring, checklist, and tag workflows. Each tool covers a meaningful operation without excessive fragmentation.
The surface covers task CRUD, scoring/progress, checklist item lifecycle, tag listing and management, and a daily overview snapshot. Core Habitica task-management workflows are complete, with no obvious dead ends for the stated purpose.