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
- 0 ★ on the repository
- Last commit
Extended access
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
- Works in
- Services
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.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates, changes, moves and deletes tasks and subtasks in the workspace
- The token grants full read and write access with no permission split
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 dateMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
WEEEK_TOKENrequired, secret- The WEEEK token, shared by the CLI and the MCP server.
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
All WEEEK toolsWEEEK MCP by names, not IDs
weeek-mcp-smart
A WEEEK MCP server creates a task from project, column and assignee names in one call, no chain of lookups for their IDs
Weeek MCP server
weeek-mcp
A local MCP server for Weeek: projects, tasks and boards are read-only by default, writes are opt-in
Python MCP server for WEEEK API v1: tasks, projects, boards, funnels, deals and contacts, with SSE mode for n8n
WEEEK MCP with a read/write split
weeek-mcp-server
A 12-tool WEEEK MCP server split into 7 read and 5 write tools, so an MCP client can auto-approve the safe ones
WEEEK MCP with confirm-gated writes
weeek-mcp
A WEEEK MCP server that is read-only by default: tasks, attachments and comments via a browser session, writes are opt-in
An MCP server for Weeek: projects, boards, tasks and time tracking with reports right from Claude Code
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.