weeek-mcp-smart
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEEEK_API_TOKEN | Yes | Your WEEEK API token from Settings → API → generate a personal token. |
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_versionA | Return this MCP server's name and version, so callers can check which build is running. |
| weeek_list_projectsA | List WEEEK projects: id, name, isPrivate, status and portfolioId. Use weeek_get_project for a project's description and team. |
| weeek_list_boardsA | List the boards of a WEEEK project (by name or id): id, name, privacy. Use it to find a board for weeek_move_task or weeek_list_columns. |
| weeek_list_columnsA | List the columns of a WEEEK board: id, name, boardId. Pass the board by id, or by name together with its |
| weeek_list_tasksA | List WEEEK tasks with server-side filters: project, board, column, assignee (userId), completion, free-text |
| weeek_get_taskA | Get one WEEEK task by id: assignees, watchers, parent and subtasks, priority, dates, tags, locations, time entries, attachments and custom-field values ( |
| weeek_get_attachmentA | Read one WEEEK attachment by id. For an image WEEEK hosts itself this returns the image, so a task whose requirements live in a screenshot can actually be read instead of guessed at from the surrounding text; anything else comes back as metadata. Ids come from a task's |
| weeek_list_membersA | List WEEEK workspace members (id + display name). Any tool that takes an assignee, watcher or member accepts these names directly; use this to see who exists. |
| weeek_create_taskA | Create a WEEEK task. Accepts project/column/assignee by NAME or id, a natural-language |
| weeek_create_tasksA | Create up to 50 WEEEK tasks in one call. Each item takes the same fields as weeek_create_task: |
| weeek_update_taskA | Update a WEEEK task: title, natural-language |
| weeek_delete_taskA | Permanently delete a WEEEK task by id. Irreversible — the task is removed, not just completed. Requires confirm:true; to merely close a task use weeek_complete_task instead. |
| weeek_attach_fileA | Attach a local file to a WEEEK task. For safety only files inside the allowed directory (the server's working directory by default, or WEEEK_ATTACH_DIR if set) — and its subfolders — may be attached; paths outside it are refused. |
| weeek_move_taskA | Move a WEEEK task to a column (by name or id, scoped to the given board) on that board. Find board ids with weeek_list_boards. |
| weeek_complete_taskA | Mark a WEEEK task complete, or reopen it (completed:false). |
| weeek_list_commentsA | List the comments on a WEEEK task: id, author member id, markdown, reply parent, timestamps. Paged; |
| weeek_add_commentA | Add a markdown comment to a WEEEK task as the token's owner. Pass |
| weeek_delete_commentA | Permanently delete one comment from a WEEEK task. Irreversible; requires confirm:true. |
| weeek_add_assigneesA | Assign one or more workspace members (by name or id) to a WEEEK task, keeping the existing assignees. Returns the task. |
| weeek_remove_assigneesA | Unassign one or more members (by name or id) from a WEEEK task. Requires confirm:true. Returns the task. |
| weeek_add_watchersA | Add members (by name or id) as watchers of a WEEEK task, so they get its notifications. Returns the task; watchers are its |
| weeek_remove_watchersA | Stop members (by name or id) watching a WEEEK task. Requires confirm:true. Returns the task. |
| weeek_add_task_to_projectA | Show a WEEEK task in another project too (a task can live in several). Project and optional column by name or id. To move between boards of one project use weeek_move_task. |
| weeek_remove_task_from_projectA | Remove a WEEEK task from one of its projects (by name or id); the task keeps its other projects. Requires confirm:true. |
| weeek_set_task_parentA | Make a WEEEK task a subtask of |
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 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.