Personal OS MCP
Related Servers
Alternatives to Personal OS MCP
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceMCP 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.1211 npmMIT- AlicenseAqualityBmaintenanceLocal, 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.1027 npmMIT
- AlicenseNot gradedqualityBmaintenanceA local-stdio MCP server for a single personal Todoist account with env-gated read-only mode and prompt-injection mitigations.126 npmMIT
- FlicenseBqualityBmaintenanceLocal MCP server for essential ClickUp workflows over stdio, exposing a bounded set of tools for search, task management, comments, tags, and workspace hierarchy.32-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the Taskwarrior CLI to allow AI assistants to create, query, modify, and manage tasks directly from agentic coding tools.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a stdio MCP server that drives structured multi-agent development workflows: claiming and updating tracked tasks, logging actions and handoffs, gating work on server-owned health checks, and managing use-case, functional, and technical specification documents on the filesystem. It also exposes read-only skills for triage, consultation, review, and product guidance while enforcing approval and repair authorizations.29 npmMIT
TDQS
Scored across 66 tools
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.
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.
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.
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.