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.10035 npmMIT
- 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.35 npmMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to manage Super Productivity tasks, projects, and tags via its Local REST API, including task creation, updates, starting, stopping, archiving, and reading status and Focus Mode state.16MIT
- AlicenseAqualityDmaintenanceEnables AI coding agents to read and write WEEEK projects, boards, tasks, and comments directly, without context switching.121MIT
- 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 gradedqualityBmaintenanceEnables Claude Code and OpenAI Codex to interact with the Weeek task tracker through natural language, covering task creation, searching, updating, moving, completing, commenting, and file attachments via thirteen curated tools.30 npmMIT
TDQS
Scored across 35 tools
Most tools have clearly distinct purposes with detailed descriptions that cross-reference related tools. A few pairs could be confused (e.g., move_task vs add_task_to_project, manage_time_entry vs task_timer), but the descriptions generally clarify the boundaries.
All tool names use a consistent snake_case with the weeek_ prefix and mostly follow a verb_noun pattern (list_, manage_, get_, create_, update_, delete_, add_, remove_, set_, move_, etc.). Minor deviations like 'whoami' and 'task_timer' break the pattern, and 'manage_' is used for multi-action tools, but overall the convention is predictable.
With 35 tools, the surface is heavy for a single MCP server, exceeding the typical 3-15 range. However, the breadth of the task management domain (projects, tasks, boards, columns, comments, custom fields, tags, time tracking, attachments, members, assignments, portfolios) justifies many of them, though some consolidation could still reduce the count.
The tool set covers core CRUD and lifecycle operations for most entities: projects, tasks, boards, columns, comments, custom fields, tags, time entries, attachments, assignees, watchers, and portfolios. Notable gaps include no list operation for time entries or attachments (only create/get), and no direct read of a single project or board, but these are minor and workable around.