A
licenseNot graded
qualityD
maintenanceMCP 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.
2 npm
11
MIT
TaScan MCP Server
by snowbikemike
Related Servers
Alternatives to TaScan MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to manage workspaces, projects, tasks, and AI agents through natural language, with hosted or local connection options and OpenAPI-to-MCP tool generation.1,927 npmMIT
- 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.10066 npm4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and IDEs to manage workspaces, projects, tasks, and AI agents through natural language, including creation, updates, completion, assignment, and automation. It also supports generating MCP tools from arbitrary OpenAPI specs for broader API integration.1,927 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to manage Taskade workspaces, projects, tasks, and AI agents through natural language, with hosted OAuth or local token-based access.1,927 npmMIT
- AlicenseAqualityCmaintenanceMCP 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.558 npmISC
TDQS
A3.5/5.0
Scored across 69 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count1/5
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.
Completeness4/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues