# weeek-mcp [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/YOLKINS/weeek-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 240  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/weeek-mcp

## Description
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "weeek-mcp": {
    "command": "npx",
    "args": ["-y","weeek-mcp"],
    "env": {
      "WEEEK_ACCESS_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `WEEEK_ACCESS_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What weeek-mcp does

The weeek-mcp MCP server gives AI clients access to a Weeek workspace through the Weeek public API. It is intended for local use and communicates with the client over stdio rather than a network-facing MCP endpoint. The default configuration is read-only, which lets an agent inspect workspace data without registering mutation tools.

The read-only tool set includes account verification, project listing and lookup, task listing and lookup, member and tag listing, and board and board-column inspection. Task listing supports filters and offset-based pagination. Task responses can include multi-assignee fields, while project lookup includes the project description.

The project belongs in the Workplace & Productivity category for workflows that connect an assistant with project and task-management data.

## How it works

The server runs locally under Node.js 20 or newer. The recommended launch method uses `npx -y weeek-mcp`, which downloads and caches the npm package without requiring a repository clone or build step. An MCP client starts the process and passes configuration through its environment block. Requests are then made to Weeek using the supplied personal API token.

By default, only tools marked as read-only are registered. Setting `READ_ONLY=false` adds five write tools: task completion, task movement between board columns, task creation, task updates, and merge-request link assignment. `ENABLED_TOOLS` can narrow the registered set, but it cannot enable writes unless the outer `READ_ONLY` gate is disabled.

Responses are limited by `MAX_RESPONSE_CHARS`; oversized payloads are clipped and marked with `truncated: true`. Startup configuration is validated, and invalid values cause the process to exit with an error.

## Setup and configuration

Install the weeek-mcp MCP server through an MCP client configuration using the `npx` command and provide `WEEEK_ACCESS_TOKEN`. The token can be generated from the API settings in a Weeek workspace. Claude Desktop, Cursor, and Cline use an `mcpServers` configuration shape; the repository includes example files for these clients.

Required and optional environment variables include:

- `WEEEK_ACCESS_TOKEN`: required personal Weeek API token.
- `WEEEK_BASE_URL`: optional API base URL, defaulting to `https://api.weeek.net/public/v1`.
- `WEEEK_TIMEOUT_MS`: optional positive request timeout in milliseconds.
- `READ_ONLY`: defaults to `true`; use `false` to expose write tools.
- `ENABLED_TOOLS`: optional comma-separated tool allowlist.
- `MAX_RESPONSE_CHARS`: response-size limit, defaulting to `65536`.
- `LOG_LEVEL`: logger threshold, defaulting to `info`.

The process does not load a `.env` file itself, so variables must be supplied by the client or shell.

## Tools and capabilities

The default installation exposes ten read tools:

- Check transport health with `ping`.
- Confirm the authenticated account with `weeek_get_me`.
- List or retrieve projects, tasks, members, tags, boards, and board columns.
- Filter and paginate task listings.

With writes enabled, the weeek-mcp MCP server exposes five additional tools. It can complete or reopen a task, move it to a board column, create a task, update selected task fields, and store a merge or pull-request URL in a custom field. The server cannot delete tasks, so a created task cannot be removed through these tools.

## Limitations and notes

Write access changes the workspace reached by the token and is not protected by a server-side confirmation prompt. Creating a task is not reversible through this server, and retrying a create operation can produce a duplicate. Moving or updating tasks may also require knowing the previous value to restore it.

`ENABLED_TOOLS` is intersected with `READ_ONLY`; naming a write tool alone does not expose it. The access token must be valid and free of surrounding whitespace or placeholder text. The server supports the MCP 2025-06-18 version according to the repository metadata.

_Full upstream README: https://allmcps.com/mcp/weeek-mcp/readme_