First stable release. Installs with npx weeek-mcp.
Breaking change from 0.3.0
WEEEK_API_TOKEN has been removed. It was an alias; the server now reads
only WEEEK_ACCESS_TOKEN and refuses to start without it. If you are upgrading
and your client config still sets the old name, the server will exit at startup
rather than run unauthenticated.
- "env": { "WEEEK_API_TOKEN": "your-token" }
+ "env": { "WEEEK_ACCESS_TOKEN": "your-token" }What it does
Ten read tools are exposed by a default install: ping, weeek_get_me,
weeek_list_projects, weeek_get_project, weeek_list_tasks,
weeek_get_task, weeek_list_members, weeek_list_tags,
weeek_list_boards, weeek_list_board_columns.
Five write tools — weeek_create_task, weeek_update_task,
weeek_move_task, weeek_complete_task, weeek_set_task_mr_link — appear
only under READ_ONLY=false. A fresh install cannot mutate your workspace
without that explicit opt-in.
The tool surface is unchanged from 0.3.0 and verified so by test.
Notes
- stdio transport, MCP protocol
2025-06-18; requires Node >= 20. stdoutbelongs to JSON-RPC and carries nothing else — logs go tostderr
as NDJSON with recursive redaction of credentials. Both are enforced by
tests, not convention.- Published from CI with npm provenance;
verify withnpm audit signatures. - Tool reference: docs/tools.md ·
errors: docs/errors.md