Skip to main content
Glama

weeek-mcp

A Model Context Protocol server for Weeek — drive projects, boards, tasks, assignees, comments, tags and time tracking from any MCP client (Claude, Cursor, …). Every action is attributed to the owner of your Weeek API token.

Run

Needs Node 18+. Create a token in Weeek → workspace → Settings → API.

WEEEK_API_TOKEN=xxxxx npx weeek-mcp

From source:

npm install && npm run build
WEEEK_API_TOKEN=xxxxx node dist/index.js

Related MCP server: weeek-mcp

Configure your MCP client

Claude Code / Claude Desktop (.mcp.json or claude_desktop_config.json):

{
  "mcpServers": {
    "weeek": {
      "command": "npx",
      "args": ["weeek-mcp"],
      "env": { "WEEEK_API_TOKEN": "xxxxx" }
    }
  }
}

Env

Default

WEEEK_API_TOKEN

—

required; the server acts as this token's owner

WEEEK_API_BASE

https://api.weeek.net/public/v1

override the API base

Tools

  • Navigate — weeek_list_projects · weeek_list_members · weeek_list_boards · weeek_list_board_columns · weeek_list_tags · weeek_list_tasks · weeek_list_comments

  • Create / change — weeek_create_board · weeek_create_task (board/column, assignees, due date, priority 0–3, tags, subtask via parentId) · weeek_update_task · weeek_complete_task

  • Collaborate — weeek_add_comment (markdown) · weeek_log_time (minutes)

Tags and members are referenced by id (via the list_* tools). Custom-field values depend on the field type (text = string, select = option id). On any error the server returns Weeek's own response body, so a wrong field is easy to spot.

Dev

npm run build   # tsc → dist/

MIT © ApeHub

Available Tools

13 tools
weeek_add_commentA

Add a comment to a task (markdown).

Inputs: taskId (required), markdown (required).

weeek_complete_taskC

Mark a task completed by its id.

Inputs: taskId (required).

weeek_create_boardC

Create a board in a project.

Inputs: name (required), projectId (required).

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).

Inputs: title (required), tags, boardId, dueDate, +6 more.

weeek_list_board_columnsB

List the columns of a board — use a column id to place a task.

Inputs: boardId (required).

weeek_list_boardsC

List boards in a project (id, name).

Inputs: projectId (required).

weeek_list_commentsC

List a task's comments.

Inputs: taskId (required).

weeek_list_membersA

List workspace members (id, name, email, role). Use a member id as an assignee.

Inputs: no named parameters.

weeek_list_projectsB

List Weeek projects in the workspace.

Inputs: no named parameters.

weeek_list_tagsA

List workspace tags (id, title) — pass a tag id to a task's tags.

Inputs: no named parameters.

weeek_list_tasksC

List Weeek tasks, optionally filtered by project id.

Inputs: projectId.

weeek_log_timeB

Log a time entry on a task. duration is in minutes; userId comes from weeek_list_members.

Inputs: date (required), taskId (required), userId (required), duration (required).

weeek_update_taskB

Update a task. assignees (member ids) REPLACE the assignee list. Other fields change only if passed.

Inputs: taskId (required), tags, title, dueDate, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Full-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.
      2
      -
    • A
      license
      C
      quality
      D
      maintenance
      MCP server for WEEEK Public API v1 enabling management of tasks, projects, boards, tags, custom fields, time tracking, and CRM entities.
      100
      56 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-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.
      56 npm
      MIT