ffxiv-daily-reset-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FFXIV_RESET_STORE | No | Path to the local JSON file where tracked chores are stored. Defaults to the first match of $XDG_DATA_HOME/ffxiv-reset-mcp/tasks.json, otherwise ~/.local/share/ffxiv-reset-mcp/tasks.json. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_resetsA | Show the next FFXIV daily, grand-company, and weekly reset times in UTC with countdowns. No arguments. |
| list_charactersA | List all characters that have tracked chores. |
| list_tasksB | List chores and their reset-window status. Optional filters: character, category (gc_turnin, duty_support, beast_tribe, item_turnin, custom). |
| add_taskB | Track a per-character chore. Required: character, title. Optional: category (default custom), cadence (daily|gc|weekly|rolling; gc = 20:00 UTC turn-in window), period_hours (rolling cadence only), notes, allowance (e.g. beast tribe allowance count). |
| complete_taskB | Mark a chore completed (completed_at = now). Use the numeric task id. |
| uncomplete_taskB | Undo a completion (clears completed_at). |
| delete_taskC | Remove a tracked chore entirely. |
| summaryA | Return a readable due/overdue report the agent can paste into chat. Optional character filter. Best default reply for 'what are my FFXIV chores?' |
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 8 tools
Most tools have clearly distinct purposes: reset times, character listing, task CRUD, and summary reporting. The only mild overlap is between list_tasks and summary, since both expose chore status, but the descriptions clarify structured listing versus a readable due/overdue report.
Seven of eight tools follow a predictable verb_noun or action-oriented pattern such as list_tasks, add_task, complete_task, and delete_task. The lone noun-only 'summary' is a minor deviation, and 'uncomplete_task' is awkward but still consistent with complete_task.
Eight tools is well-scoped for a chore-tracking server with reset awareness. Each tool covers a distinct lifecycle operation or reporting need without excessive surface area.
The core lifecycle is covered: add, list, complete, uncomplete, delete, character listing, reset times, and summary reporting. The notable gap is updating an existing task's fields, though delete-and-re-add is a workable fallback.