Weeek MCP logo

Weeek MCP

Connect AI clients to Weeek over stdio with read tools by default and optional task-writing tools.

Install Weeek MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "weeek-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "weeek-mcp"
      ],
      "env": {
        "WEEEK_ACCESS_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y weeek-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

weeek-mcp MCP server connects supported AI clients to a Weeek workspace over local stdio transport. It exposes ten read tools by default for projects, tasks, boards, members, tags, and account details. Set READ_ONLY=false to register five additional tools for creating, editing, moving, completing tasks, or recording merge-request links. Reach for it when an agent needs controlled access to Weeek data from Claude Desktop, Cursor, Cline, or another MCP client.

Use cases

  • List Weeek projects and tasks for an assistant
  • Inspect boards, columns, members, and tags
  • Create and update tasks with write access enabled
  • Record merge-request links on Weeek tasks
  • Verify a Weeek API token and transport connection

Key features

  • Read-only-by-default tool registration
  • Project, task, board, member, and tag queries
  • Optional task creation and mutation tools
  • Tool allowlisting with ENABLED_TOOLS
  • Response-size limits with truncation flags
  • Local stdio transport

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16h ago via OSV.dev · weeek-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads240Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Weeek MCP works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Weeek MCP

Configure an MCP client to run `npx -y weeek-mcp` and pass a valid `WEEEK_ACCESS_TOKEN` in the environment.

Yes. The repository provides a Claude Desktop configuration example using the `mcpServers` format.

Set `READ_ONLY=false`. You can also set `ENABLED_TOOLS` to restrict which tools are registered.

It can read the authenticated user, projects, tasks, workspace members, tags, boards, and board columns.

No. The available write tools do not include task deletion.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWeeek MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/weeek-mcp?style=directory)](https://allmcps.com/mcp/weeek-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/weeek-mcp"><img src="https://allmcps.com/api/badge/weeek-mcp?style=directory" alt="Weeek MCP on AllMCPs" /></a>