weeek-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEEEK_API_BASE | No | Override the API base URL. | https://api.weeek.net/public/v1 |
| WEEEK_API_TOKEN | Yes | Your Weeek API token. Create a token in Weeek → workspace → Settings → API. The server acts as this token's owner. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weeek_list_projectsB | List Weeek projects in the workspace. |
| weeek_list_membersA | List workspace members (id, name, email, role). Use a member id as an assignee. |
| weeek_list_boardsC | List boards in a project (id, name). |
| weeek_list_board_columnsB | List the columns of a board — use a column id to place a task. |
| weeek_list_tagsA | List workspace tags (id, title) — pass a tag id to a task's tags. |
| weeek_list_tasksC | List Weeek tasks, optionally filtered by project id. |
| weeek_list_commentsC | List a task's comments. |
| weeek_create_boardC | Create a board in a project. |
| weeek_create_taskB | Create a task. Optionally place it on a board/column, assign members (ids from weeek_list_members), set a due date (YYYY-MM-DD), priority (0–3), tags (ids), or a parent (→ subtask). |
| weeek_update_taskB | Update a task. assignees (member ids) REPLACE the assignee list. Other fields change only if passed. |
| weeek_add_commentA | Add a comment to a task (markdown). |
| weeek_log_timeB | Log a time entry on a task. duration is in minutes; userId comes from weeek_list_members. |
| weeek_complete_taskC | Mark a task completed by its id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.