SkillFoxx

WEEEK MCP with a read/write split

weeek-mcp-server

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

  • 1 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Can create, update and complete tasks in the workspace
  • The API token is not read-only by itself; restriction is only possible on the MCP client side
All reasons and checks
Russian stack

makarglavanar/weeek-mcpAuthor:MakarGlavanar

Install

Services

Manual install

{
  "mcpServers": {
    "weeek": {
      "command": "npx",
      "args": ["-y", "weeek-mcp-server"],
      "env": {
        "WEEEK_API_TOKEN": "your-weeek-token-here"
      }
    }
  }
}

The README's Claude Desktop config; Cursor uses the same shape in ~/.cursor/mcp.json.

Access and checks

How we review

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

  • Can create, update and complete tasks in the workspace
  • The API token is not read-only by itself; restriction is only possible on the MCP client side

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

What it does

The server gives access to WEEEK projects, boards, tasks and comments through 12 tools, explicitly split into read (projects, boards, columns, tasks, comments) and write (create, update, move and complete a task, post a comment). The split is deliberate so MCP clients can configure auto-approval for read tools only, leaving writes under manual control. List tools paginate at 20 by default, capped at 50, to stay under the 25k-token MCP response limit. API failures return structured with isError: true and a human-readable message, without crashing the server. It installs and runs via npx with no separate setup.

Who it is for. For people who want their MCP client to auto-approve WEEEK reads while requiring confirmation for writes.

Good fit when

  • You want to separate auto-approved reads from confirmation-gated writes in client settings
  • You need large task lists without risking the MCP response limit
  • You need to work with task comments alongside the tasks themselves

Not a fit when

  • You need WEEEK's knowledge base or CRM parts, the server only covers tasks
  • You need a CLI alongside the MCP, this ships only the server

Example request

Show my open tasks in the Website project and move task 42 to the Done column

MCP

Transport
stdio
Authentication
API key

Environment variables

WEEEK_API_TOKEN required, secret
A personal WEEEK token, granting full read and write access to the workspace.

Limitations

The server has no repository description; it needs a WEEEK API token with full workspace rights. Coverage is limited to tasks, boards and comments.

How to disable. Remove the weeek server from your MCP client configuration and revoke the token in WEEEK settings.

FAQ

Can I restrict the agent to WEEEK reads only?

Yes, tools are explicitly split into read and write, so the client can be configured to auto-approve only the read set.

What happens if a task list is too large?

List tools paginate at 20 items by default, capped at 50, so the response stays under the MCP 25k-token limit.

Discussion

No questions or reviews yet.

All WEEEK tools
Russian stack

A WEEEK MCP server that is read-only by default: tasks, attachments and comments via a browser session, writes are opt-in

MCP serverExtended access
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 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
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

Comparison with similar tools

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

ToolOfficialAuthenticationRepository starsMain difference
WEEEK MCP with a read/write split (this card)noAPI key1
Weeek MCP ServernoAPI key2tasks, CRM and SSE for n8n
WEEEK MCP by names, not IDsnoAPI key4creates tasks by names, no IDs
WEEEK MCP with confirm-gated writesnoAPI key0writes on request

README in short

The README lists 12 tools with an explicit read/write split and explains the motivation: MCP clients can auto-approve reads and require confirmation for writes. It describes safe pagination defaults, a single WEEEK_API_TOKEN variable, structured error handling, and configs for Claude Desktop and Cursor via npx with no install.

README badge

Report a problem