amazing-marvin-complete-mcp
Related Servers
Alternatives to amazing-marvin-complete-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA personal assistant MCP server that integrates Todoist, Anki, Obsidian, and Google Calendar to help you learn, organize, and stay productive through natural language interactions.2-
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to interact with the Taskwarrior command-line task management tool. It allows users to list, create, modify, and organize tasks using projects, tags, and annotations through natural language.132MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that connects AI assistants to Super Productivity for managing tasks, projects, and tags. Supports quick capture, batch triage, and full planning sessions through natural language.90 npm85MIT
- FlicenseAqualityBmaintenanceMCP server exposing Zentra's Task API as tools for Claude, enabling task creation, listing, and moving via natural language from any project.3-
- AlicenseAqualityAmaintenanceAn MCP server that connects ChatGPT Desktop or Codex to Super Productivity's local REST API, enabling explicit task selection, planning, timer control, and completion via natural language.1019 npmMIT
- AlicenseBqualityCmaintenanceAn MCP server that lets your AI assistant manage TickTick tasks, projects, habits, and more through natural language, supporting both TickTick and Dida365.521MIT
TDQS
Scored across 37 tools
Most tools have clear distinct purposes, but there is semantic overlap: update_task vs set_priority (explicitly warns to use set_priority for priority), mark_done vs update_task, and create_category_or_project vs convert_category_or_project. The descriptions are exceptionally detailed and often clarify boundaries, preventing lower scoring, but an agent must read carefully to avoid misselection.
The vast majority follow a consistent snake_case verb_noun pattern (get_*, create_*, update_*, delete_*, mark_done, unmark_done, start_tracking, stop_tracking). A couple of deviations like 'mark_done' (verb without explicit object) and 'test_connection' are minor and readable.
37 tools is heavy for a task-management API integration. While the domain is broad (tasks, projects, categories, habits, rewards, time tracking, calendar, reminders), many tools could be consolidated (e.g., separate getters for today, due, done, children), and the count strains the 'well-scoped' ideal.
The surface covers a large portion of the domain with CRUD for tasks, categories/projects, time tracking, rewards, reminders, habits, and read operations for various views. Some gaps exist (e.g., no dedicated tool to set task time/reminder fields, no batch operations), but agents can work around most missing operations via update_task or other tools.