weeek-mcp
Related Servers
Alternatives to weeek-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceMCP server for WEEEK Public API v1 enabling management of tasks, projects, boards, tags, custom fields, time tracking, and CRM entities.10053 npmMIT
- AlicenseAqualityBmaintenanceMCP server that lets an agent work with the Weeek task manager: view boards, create, update and move tasks and subtasks, write and delete its own comments, attach and download files, and build time reports. It keeps project-specific boards, columns and conventions in a committed .weeek.json, and is read-only-safe, token-scoped, and limited to allowed attachment folders.11MIT
- AlicenseBqualityAmaintenanceEnables task management on Weeek via the public REST API and knowledge base browsing as MCP resources with full document content.35212 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceFull-featured MCP server integrating all 71 endpoints of the Weeek API as MCP tools for AI clients, enabling task, project, and workspace management via natural language.3-
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for the Weeek Public API. Use it from Cursor or Claude Code to browse projects, search tasks, read attachments, and (with a browser session) load task comments.53 npmMIT
- AlicenseAqualityAmaintenanceWEEEK MCP server that allows creating, reading, updating, moving, and completing tasks using names instead of IDs for projects, columns, and assignees.12258 npm2MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: list_* tools cover different entities (projects, members, boards, columns, tags, tasks, comments) with no overlap, and the mutation tools (create_board, create_task, update_task, complete_task, add_comment, log_time) are clearly differentiated. complete_task is a minor convenience wrapper over update_task, but the boundaries remain unambiguous.
Every tool follows the identical weeek_verb_noun pattern (weeek_list_tasks, weeek_create_task, weeek_update_task, etc.), with a consistent prefix and verb-first convention throughout. No mixing of camelCase or alternate verb styles.
13 tools is well within the ideal 3-15 range for a task/project management integration. Each tool earns its place covering a distinct read or write operation, with no redundant or filler tools.
Core task lifecycle is covered (create, update, complete, comment, log time) with good read coverage across projects, members, boards, columns, tags, and comments. Gaps remain: no delete operations anywhere (tasks, comments, boards) and no project creation or board/column mutation beyond create_board, but agents can accomplish most workflows.