claude-weeek

Claude Code plugin for the WEEEK tracker: tasks and boards via MCP, skills for starting a task, standups and status moves

PluginHigh riskRussian stack

notcodev/claude-weeek

Install

/plugin marketplace add notcodev/notcodev-marketplace
/plugin install claude-weeek@notcodev-marketplace

Restart the session if the tools do not appear.

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 progress

Limitations

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.

Security check

  • Creates, edits and completes tasks in a live workspace
  • The token grants full access to the WEEEK workspace

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.

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.

Editors’ pick

A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more

CLIHigh risk31K
Editors’ pick

Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server

CLIMedium risk29.7K
Editors’ pick

A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI

MCP serverMedium risk28.1K
Editors’ pick

Anthropic's official plugins for knowledge work roles: sales, support, product, marketing, legal, finance, data and enterprise search

PluginHigh risk24K