Skip to main content
Glama
Sign In
ffxiv-daily-reset-mcp-server

ffxiv-daily-reset-mcp-server

by OpenCode-Projects-AtlasRearden8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ffxiv-daily-reset-mcp-server

No user-submitted related servers found.

    Related Servers

    • Task / To-Do Manager

      laibaafreen
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI assistant to manage a simple to-do list stored in a local JSON file, with tools to add, list, get, complete, and delete tasks, plus a read-only pending tasks resource.
      -

    • Library Loans MCP Server

      OpenCode-Projects-AtlasRearden8
      A
      license
      A
      quality
      B
      maintenance
      Enables users and AI agents to track borrowed physical library books locally, including recording loans, renewals, returns, holds, due-soon and overdue queries, and per-branch tallies, with all data stored in a local JSON file.
      11
      MIT

    • Task MCP Server

      m-higuchi
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to manage todo tasks through Tools for adding, listing, completing, and searching, alongside Prompts for daily reviews and task breakdowns. Exposes task lists and statistics as Resources with local JSON file persistence.
      -

    • jsony-mcp

      vcosmin2701
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read, write, query, and manage JSON data files with automatic ID and timestamp generation.
      6
      16 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources