WEEEK CLI and MCP on Bun
Weeek CLI + MCP Server
A weeek CLI command and an MCP server for WEEEK in one Bun package: projects, boards, tasks and subtasks from a terminal or an agent
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Creates, changes, moves and deletes tasks and subtasks in the workspace
- The token grants full read and write access with no permission split
Install
Manual install
bun install && export WEEEK_TOKEN="your-weeek-api-token" && bun run buildInstall from the README; after building, both the weeek and weeek-mcp binaries are available.
This is third-party code. Review the repository files before installing.
What it does
The package offers two entry points into the same WEEEK Public API functionality: the weeek CLI command for manual calls and scripts (listing and creating projects, members, boards, columns, tasks with an assignee and due date, subtasks, and moving a task between a column, a board, or even a project) and the weeek-mcp server, which exposes the same operations to an agent over stdio. Both use the same token from the WEEEK_TOKEN variable or the CLI's --token flag.
Who it is for. For people who want both a manual CLI for scripts and MCP access for an agent to the same WEEEK logic.
Good fit when
- You want both a terminal CLI and an MCP server from one codebase with no behavior drift
- You need to move tasks between projects, not just between columns of one board
- You work with Bun and want a lightweight package with no Node dependencies
Not a fit when
- You do not have Bun and do not want to install it for one tool
- You need WEEEK's CRM part or knowledge base, the package is focused on projects, boards and tasks
Example request
Create a Ship feature task in project 123 on board 456 with an assignee and a 2026-05-10 due dateLimitations
Requires the Bun runtime rather than plain Node.js. No license is stated in the repository. Coverage is limited to projects, members, boards, columns, tasks and subtasks, with no CRM or knowledge base.
How to disable. Remove the weeek-mcp binary from your MCP client configuration and the WEEEK_TOKEN variable from your environment.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| WEEEK_TOKEN required, secret | The WEEEK token, shared by the CLI and the MCP server. |
Security check
- Creates, changes, moves and deletes tasks and subtasks in the workspace
- The token grants full read and write access with no permission split
README in short
The README shows installation via bun install and a build step, setting the token via WEEEK_TOKEN or the --token flag, a full list of CLI commands for projects, members, boards, columns and tasks with examples like creating a task with an assignee and due date, subtask-create, and three ways to move a task (move, move-board, move-project). It separately covers running the MCP server from the same build under the name weeek-mcp.
FAQ
Can I use just the CLI without connecting the MCP?
Yes, the weeek command works independently of the MCP server; both use the same token and API.
Can a task be moved to a different project?
Yes, a separate tasks move-project command moves a task from one project to another with a target column.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI