Skip to main content
Glama

Related Servers

Alternatives to mstodo-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Exposes Microsoft To Do and Microsoft Planner over the Microsoft Graph API with delegated authentication, letting an assistant read and write personal tasks, checklists, and shared team tasks—including assigning Planner tasks to other people—and also search OneNote notebooks and pages read-only.
      38
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive Microsoft To Do task management through Microsoft Graph API with Entra ID OAuth authentication. Supports creating, updating, and managing todo lists, tasks, reminders, and due dates through natural language.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Microsoft To Do tasks via the Graph API, supporting multiple accounts, encrypted auth, and full CRUD operations.
      2
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables users to manage a persistent todo list through natural language, supporting adding, listing, toggling completion status, and removing todos. Features both stdio and HTTP transports with optional authentication and JSON file storage.
      4
      ISC

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but there are overlapping boundaries: update_task can mark a task completed, making complete_task redundant, and login_status overlaps with list_providers for checking auth state. Descriptions help clarify intended use, but an agent could still struggle to choose between these pairs.

    Naming Consistency4/5

    Task and list tools consistently follow a verb_noun pattern: list_tasks, create_task, delete_task_list, move_task_between_lists. The auth tools (login, login_status, logout) deviate from that pattern, but they form their own predictable auth-related group, so the overall naming is mostly consistent.

    Tool Count4/5

    Fifteen tools is on the upper end of the ideal range but is reasonable for a Microsoft To Do bridge covering auth, providers, task lists, and individual tasks. A few tools like complete_task and list_providers feel somewhat redundant, suggesting the count could be trimmed slightly, but it is not excessive.

    Completeness4/5

    The server covers the core lifecycle well: list, create, get, update, complete, delete, search, and move tasks, plus list and auth management. Minor gaps exist, such as no way to rename a task list and no dedicated get_task_list operation, but agents can work around these with the available tools.