Skip to main content
Glama
likalg

Personal OS MCP

by likalg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Personal OS MCP

No user-submitted related servers found.

    Related Servers

    • @batontasks/mcp by batontasks

      @batontasks/mcpofficial

      batontasks
      A
      license
      B
      quality
      B
      maintenance
      MCP server for the Baton task tracker, enabling AI agents to manage tasks, process inbox events, and collaborate with humans via natural language. Wraps the Baton REST API with 12 tools over stdio.
      12
      17 npm
      MIT
    • weeek-mcp by YOLKINS

      weeek-mcpofficial

      YOLKINS
      A
      license
      A
      quality
      B
      maintenance
      Local, read-only-by-default MCP server for Weeek that connects AI clients to your workspace over stdio, enabling listing projects, tasks, boards, members, and tags with opt-in write tools for task management.
      10
      57 npm
      MIT

    • todoist-mcp

      kevlasher
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-stdio MCP server for a single personal Todoist account with env-gated read-only mode and prompt-injection mitigations.
      273 npm
      MIT

    • questlog-mcp

      JoeyMckenzie
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Taskwarrior CLI to allow AI assistants to create, query, modify, and manage tasks directly from agentic coding tools.
      7 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.5/5.0

    Scored across 66 tools

    Disambiguation5/5

    Each tool targets a specific resource and action (e.g., list_tasks vs. list_notes; archive_project vs. archive_container). Subtle distinctions like restore_task (Trash recovery) vs. unarchive_task (archive restoration) are clearly documented, reducing ambiguity despite the large surface.

    Naming Consistency5/5

    All tools follow a strict `personal_os_<verb>_<noun>` pattern in snake_case. Verbs are consistent across resources (list, get, create, update, archive, restore, delete), and special operations like `move_task_to_trash` and `update_task_planning` retain the same predictable style.

    Tool Count1/5

    With 66 tools, the server is extremely heavy. The scope is broad (tasks, notes, tags, containers, projects, collections, reviews, planning), but much duplication exists—projects and collections are typed container projections with full CRUD duplication. This is a severe count that will overwhelm agents and increase misuse risk.

    Completeness4/5

    The lifecycle coverage for tasks, notes, tags, containers, projects, collections, and reviews is comprehensive—including create/read/update/archive/restore/delete or trash. Minor gaps exist, such as no dedicated checklist management tools (checklists are referenced in mixed feeds) and no permanent task deletion, but the core domain is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources