claude-weeek plugin
Claude Code plugin for the WEEEK tracker: tasks and boards via MCP, skills for starting a task, standups and status moves
- 3 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates, edits and completes tasks in a live workspace
- The token grants full access to the WEEEK workspace
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/claude-weeekDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates, edits and completes tasks in a live workspace
- The token grants full access to the WEEEK workspace
This is third-party code. Review the repository files before installing.
What it does
The plugin registers an MCP server with read tools for projects, boards, columns and tasks and write tools to create, edit, move and complete tasks. There is deliberately no delete. Five skills cover the work loop: pick up a task and suggest a branch, list today's tasks, build a standup from commits, move a task to the next stage and summarize a task. Two hooks spot a task ID in the branch name or commit message and hint the agent without calling the API. Multiple workspaces are supported, including self-hosted.
Who it is for. For developers whose team tracks tasks in WEEEK and works in Claude Code.
Good fit when
- You want to start a WEEEK task and get a branch name right away
- You need a standup built from yesterday's commits
- You need to move tasks across board columns without opening WEEEK
Not a fit when
- You need WEEEK deals, funnels and contacts
- You do not use Claude Code
Example request
Start task WEEEK-1234 and move it to in progressLimitations
Requires Node.js 20+ and a personal WEEEK API token with full workspace access. Lists are paginated, 20 items by default. Deletes and CRM entities are not supported. The skills rely on git and settings in .weeek.json.
How to disable. Uninstall the plugin via /plugin in Claude Code, delete ~/.config/claude-weeek/config.json and revoke the token in WEEEK settings.
FAQ
Can reads be auto-approved while writes stay gated?
Yes, read and write tools are registered as separate groups, so you can auto-approve only reads.
How do I adapt it to my board?
Put a .weeek.json in the repo root with a branch template, task ID patterns and a mapping of stages to column names.
Discussion
No questions or reviews yet.
Related
All WEEEK toolsWEEEK plugin with 12 curated tools
weeek-mcp
A Claude Code and Codex plugin for WEEEK: 12 curated, not auto-generated tools, with the token in the OS keychain
Weeek MCP server
weeek-mcp
A local MCP server for Weeek: projects, tasks and boards are read-only by default, writes are opt-in
WEEEK 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
An MCP server for Weeek: projects, boards, tasks and time tracking with reports right from Claude Code
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
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
README in short
The README explains getting a WEEEK token, installing the plugin from the author's marketplace and running the multi-workspace setup wizard. It lists read and write tools, the global config format and the project .weeek.json. Each of the five skills is described with triggers and steps, and hooks and safety measures get their own sections. There is a troubleshooting table and a section on checking tools against the WEEEK OpenAPI spec. MIT license.