TaScan MCP Server
Related Servers
Alternatives to TaScan MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for task management that enables AI agents to read, create, update tasks, and track work sessions, allowing agents and humans to collaborate on the same task board.5 npm9MIT
- AlicenseBqualityDmaintenanceFull-featured MCP server for Taiga project management, enabling AI agents to manage projects, epics, user stories, tasks, issues, sprints, wiki pages, memberships, and roles via Taiga API v1.10023 npm2MIT
- AlicenseAqualityBmaintenanceMCP server for the Taiga project management API. Enables AI assistants to manage projects, issues, user stories, tasks, epics, sprints, and wiki pages via natural language commands.553 npmISC
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to connect to the OnTime personal workbench via MCP to manage tasks, projects, and goals through natural language, including creating sprint projects, logging progress, and querying workbench state in real time.-
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.24 npm2MIT
- AlicenseAqualityCmaintenanceAn MCP server for Tendem that enables users to complete tasks using a hybrid of AI and human agents. It allows for seamless task delegation and management within MCP-compatible clients.8102MIT
TDQS
Scored across 69 tools
Most tools map to distinct resource/action pairs, and descriptions explicitly differentiate similar names (e.g., get_worker vs. get_worker_passport, get_report vs. generate_report). However, with 69 tools across overlapping workflows like dispatch, reporting, and payments, a few boundaries require careful reading.
All tools share the tascan_ prefix and snake_case, and most follow a verb_noun pattern. A few exceptions are noun-only or verb-only (server_info, zone_compliance, find), so it is mostly consistent rather than perfect.
69 tools is far beyond the practical 3-15 range and even beyond the 25+ threshold. Although the platform is broad, this monolithic surface imposes heavy selection and context load and likely should be split or grouped.
Core lifecycle coverage is strong across projects/events/tasks/subtasks, workers, reports, invoices/payments, tags/zones/assets, and marketplace/agents. Minor gaps exist (e.g., template creation, asset update/delete, explicit issue resolution), but no major dead end for the described domain.