SkillFoxx

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

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • With writes enabled, can create, change and delete tasks in allowed projects
  • Reads comments through an imported browser session rather than the official API
All reasons and checks
Russian stack

prod-broke-again/weeek-mcpAuthor:prod-broke-again

Install

Services

Manual install

git clone https://github.com/prod-broke-again/weeek-mcp.git && cd weeek-mcp && npm install && npm run build

Install from the README; then a .env with WEEEK_API_TOKEN and optional write settings.

Access and checks

How we review

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

  • With writes enabled, can create, change and delete tasks in allowed projects
  • Reads comments through an imported browser session rather than the official API

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

What it does

The server reads WEEEK projects, boards, columns and tasks, searches and filters them, including my open tasks, reads members and tags, and reads image, txt, md, json and csv attachments. Task comments are not exposed by WEEEK's public API, so the server reads them through an imported browser session. Write tools (create, edit, move, delete a task) are off by default and require a mandatory propose-then-wait-for-confirmation-then-confirm cycle, plus a WEEEK_ALLOW_WRITE variable and an allowed-project list. WEEEK's Docs and Wiki are outside the public API and are not read; here, documents mean only task attachments.

Who it is for. For people who want to connect WEEEK to an agent safely: read-only first, with writes enabled separately and only on chosen projects.

Good fit when

  • You want a safe start: an agent reads tasks but cannot change them until you explicitly allow it
  • You need task comments, which are missing from WEEEK's public API
  • You want to restrict writes to specific projects via an allowlist

Not a fit when

  • You need WEEEK Docs and Wiki rather than just task attachments, the public API does not expose them
  • You need text extraction from PDF or DOCX attachments, v1 only supports URL and text files

Example request

Show my open tasks in the portal project and the latest comments on the most urgent one

MCP

Transport
stdio
Authentication
API key

Environment variables

WEEEK_API_TOKEN required, secret
The WEEEK workspace token from settings.
WEEEK_ALLOW_WRITE
Enables write tools, defaults to false.
WEEEK_WRITE_PROJECTS
An allowlist of project ids where writes are permitted.
WEEEK_READ_ONLY_PROJECTS
An allowlist of project ids for reading, defaults to all.

Limitations

Comments are read only through an imported browser session, not the public API. PDF and DOCX attachments do not get text extracted, only URL and text files. Writes are off by default and need explicit WEEEK_ALLOW_WRITE, a list of allowed projects, and confirmation for every action. Requires Node.js 20 or newer.

How to disable. Remove the server from your MCP client configuration and delete the .env with the token and saved session.

FAQ

Can the agent delete a task without asking?

No, write tools are off by default and require mandatory user confirmation plus WEEEK_ALLOW_WRITE enabled.

Does the server read WEEEK's wiki and docs?

No, WEEEK's public API does not expose them; the server only reads task attachments of certain formats.

Discussion

No questions or reviews yet.

All WEEEK tools
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 access1
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

A WEEEK MCP server: tasks via the public API and full knowledge-base CRUD via the internal API with a saved browser session

MCP serverExtended access2
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 access4
Russian stack

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

MCP serverBroad access2

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

Comparison with similar tools

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

ToolOfficialAuthenticationRepository starsMain difference
WEEEK MCP with confirm-gated writes (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 gives a can/cannot table: projects, boards, tasks and search yes, WEEEK Docs and Wiki no, task writes are opt-in with explicit confirmation, comments are read through a browser session, and PDF/DOCX text extraction is not yet supported. A separate environment variable table covers the token, project aliases, read and write allowlists, an attachment size cap, a directory cache TTL and a requests-per-second limit.

README badge

Report a problem