weeek-mcp-smart
Related Servers
Alternatives to weeek-mcp-smart
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.10064 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
- 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-
- 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.1064 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients to navigate and modify Weeek projects, boards, tasks, assignees, comments, tags, and time tracking through the Weeek API, with actions attributed to the API token owner.1364 npmMIT
- AlicenseNot gradedqualityCmaintenanceRead-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.64 npmMIT
TDQS
Scored across 25 tools
Boundaries are explicitly drawn: update_task covers title/dates/priority/tags/fields while assignees, watchers, parent and projects each get dedicated tools, and descriptions call this out. Single (create_task) vs batch (create_tasks), read vs write for attachments, and move_task vs add_task_to_project are all clearly distinguished. No two tools appear to do the same thing.
Every tool uses the same weeek_ prefix with a strict verb_noun snake_case pattern (list_boards, create_task, remove_assignees, add_comment). The only nominal outlier, weeek_version, is a harmless domain-standard convention. Highly predictable across all 25 tools.
At 25 tools this is at the heavy edge, but the domain (tasks, subtasks, projects, boards, columns, members, assignees, watchers, comments, attachments) legitimately justifies the scope. Each add/remove pair and lifecycle operation earns its place rather than being redundant. Slightly over the comfortable 3-15 range but defensible.
Strong lifecycle coverage: task CRUD, batch create, complete/reopen, move, subtask parenting, comment list/add/delete, attachment read/write, plus projects, boards, columns and members. Minor gaps exist (no comment edit, no attachment removal, no project/board creation) and description updates are impossible via the API, but these are documented and core workflows are covered.