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). |
| weeek_list_tasksA | List WEEEK tasks with server-side filters. Set allPages=true together with userId, startDate, and endDate to fetch every matching page inside the connector without returning unrelated workspace pages. |
| weeek_get_taskA | Get one WEEEK task by id (includes its assignees). |
| weeek_list_membersA | List WEEEK workspace members (id + display name). Use to find the id for assigning a task to someone; pass that id as |
| weeek_create_taskA | Create a WEEEK task. Accepts project/column/assignee by NAME or id, and a natural-language |
| weeek_create_tasksA | Create many WEEEK tasks in one call. Returns a per-item report; one bad name does not abort the batch. |
| weeek_update_taskA | Update an existing WEEEK task's title or due date. NOTE: description is NOT updatable — WEEEK's API silently ignores it on update; set the description at create time (weeek_create_task) or edit it in the UI. |
| 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. |
| weeek_complete_taskA | Mark a WEEEK task complete, or reopen it (completed:false). |
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 12 tools
Each tool targets a distinct resource/action: version, project listing, member listing, task CRUD, batch creation, deletion, completion, moving, and file attachment. Even create_task vs create_tasks are clearly separated by singular/plural and batch semantics. No two tools appear to overlap in purpose.
Most tools follow a consistent verb_noun pattern (list_projects, create_task, update_task, delete_task, complete_task, move_task, attach_file). The single deviation is weeek_version, which uses a noun instead of get_version, but this is minor and understandable for a status endpoint.
12 tools is well within the ideal 3-15 range and each tool serves a distinct, necessary function for the WEEEK task management domain. The count feels appropriately scoped without unnecessary duplication or bloat.
The toolset thoroughly covers the task lifecycle: create (single/batch), get/list, update (title/due), complete/reopen, move, delete, and file attachment, plus member lookup for assignment. Minor gaps include no project creation or explicit column listing, but these can be worked around via the create_task/move_task name-or-id parameters and are likely outside the server's intended scope.