Weeek MCP server for tasks and time tracking

weeek-mcp

An MCP server for Weeek: projects, boards, tasks and time tracking with reports right from Claude Code

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • The tools create and change tasks and time entries in the Weeek workspace
All reasons and checks
Russian stack

wh1tespirit/weeek-mcp

Install

Services

Manual install

python -m venv .venv && .venv\Scripts\python.exe -m pip install -r requirements.txt

The command from the README for Windows; venv paths differ on Linux/Mac.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The tools create and change tasks and time entries in the Weeek workspace

This is third-party code. Review the repository files before installing.

What it does

The Python server gives an agent access to a Weeek workspace: a list of projects, a project's boards and columns, tasks filtered by date and status, a full task card, creating and updating a task, marking it done, logging time against a task, and a grouped time summary report. It is covered by pytest tests.

Who it is for. For Weeek users who want to manage tasks and time tracking through an agent, by voice or text.

Good fit when

  • You want to create or update a Weeek task without opening the browser
  • You want to quickly log time against a task
  • You need a grouped time summary for a period

Not a fit when

  • You need Weeek areas beyond tasks, boards and time: chats, docs, CRM
  • You do not use Weeek

Example request

Create a task in the Marketing project on the Ideas board and log an hour of time against it

MCP

Transport
stdio
Authentication
API key

Environment variables

WEEEK_API_TOKEN required, secret
Weeek API token from Settings → API

Limitations

The project is maintained by one author, with no stars; the README is in Russian. It needs a Weeek API token. The create, update and complete-task tools change workspace data.

How to disable. Remove the server from your MCP client config, for example claude mcp remove weeek.

FAQ

How do I get a Weeek token?

Inside Weeek itself: Settings → API.

Discussion

No questions or reviews yet.

Russian stack

A local MCP server for Weeek: projects, tasks and boards are read-only by default, writes are opt-in

MCP serverExtended access
Russian stack

Python MCP server for WEEEK API v1: tasks, projects, boards, funnels, deals and contacts, with SSE mode for n8n

MCP serverBroad access2Repository stars
Russian stack

A WEEEK MCP server creates a task from project, column and assignee names in one call, no chain of lookups for their IDs

MCP serverExtended access4Repository stars
Russian stack

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

PluginBroad access3Repository stars

WEEEK CLI and MCP on Bun

Weeek CLI + MCP Server

Russian stack

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

MCP serverExtended access
Russian stack

A 12-tool WEEEK MCP server split into 7 read and 5 write tools, so an MCP client can auto-approve the safe ones

MCP serverExtended access1Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
Weeek MCP server for tasks and time tracking (this card)noAPI key0
Weeek MCP ServernoAPI key2tasks, CRM and SSE for n8n
WEEEK MCP by names, not IDsnoAPI key4creates tasks by names, no IDs
WEEEK MCP with a read/write splitnoAPI key1reads separate

README in short

The README lists nine tools in a table: projects, boards, filtered tasks, a task card, create, update, complete, time logging and a time report. It shows setup via venv and requirements.txt, token configuration in .env, connecting to Claude Code, and running tests via pytest.

README badge

Report a problem