MCP.Market

Weeek MCP server

by YOLKINS·io.github.YOLKINS/weeek-mcp·v1.0.1
No reviews yet

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

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars59 downloads/wk

Reviews

Write one

Nobody has reviewed Weeek yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Weeek tools (15, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • ping

    PRIMARY tool for connection sanity-check: returns 'pong: <msg>'.

  • weeek_complete_task

    PRIMARY tool for flipping a Weeek task's completion flag: completed

  • weeek_create_taskwrite action

    PRIMARY tool for filing a NEW Weeek task: pass a title and a target

  • weeek_get_me

    PRIMARY tool for confirming WEEEK_ACCESS_TOKEN works against the

  • weeek_get_project

    PRIMARY tool for fetching a single Weeek project's full detail by id,

  • weeek_get_task

    PRIMARY tool for fetching a single Weeek task by task_id ({id, title,

  • weeek_list_board_columns

    PRIMARY tool for board-column discovery: returns every column of a

  • weeek_list_boards

    PRIMARY tool for board discovery within a project: returns every

  • weeek_list_members

    PRIMARY tool for member discovery: returns every member of the

  • weeek_list_projects

    PRIMARY tool for project discovery: returns every Weeek project

  • weeek_list_tags

    PRIMARY tool for tag discovery: returns every tag defined in the

  • weeek_list_tasks

    PRIMARY tool for task discovery and filtering: returns one page of

  • weeek_move_task

    PRIMARY tool for changing a Weeek task's status: a board column IS a

  • weeek_set_task_mr_link

    PRIMARY tool for linking a Weeek task to the merge/pull request

  • weeek_update_taskwrite action

    PRIMARY tool for editing an EXISTING Weeek task: name the task_id

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • Code scan42 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Weeek compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
59
more than 48% of 12,191 servers with a package

What its tools let an agent do: 13 read · 2 change

Install Weeek in Claude Code, Cursor or VS Code

Runs npx -y weeek-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add weeek-mcp -- npx -y weeek-mcp
Add to Cursor

What the publisher says

From the Weeek repository's README, as published. We do not edit it. Read it on GitHub

weeek-mcp

Local, read-only-by-default MCP server for Weeek — with opt-in write tools.

Русская версия README

weeek-mcp connects AI clients (Claude Desktop, Claude Code, Cursor, MCP Inspector) to your Weeek workspace over stdio. It is read-only by default — a default install can list projects, tasks, boards, members and tags but change nothing — and exposes five write tools only when you opt in with READ_ONLY=false. Runs on Node ≥ 20; install with npx, no clone or build required.

Why this one

registered unless you opt in; ENABLEDTOOLS whitelists a subset and MAXRESPONSE_CHARS caps every payload. Server-side, not client convention.

  • On npm. npx -y weeek-mcp works today — no clone, no build, no absolute paths.
  • Read-only by default, with composable gates. Writes are simply not

messages, so a model knows when to retry versus give up without parsing prose.

  • Bilingual. Full EN ↔ RU documentation parity.
  • Granular error model. Nine distinct error codes with agent-readable

Quickstart

The recommended install path is npx — no clone, no build. Drop examples/claudedesktop.mcp.json into your MCP client config, replace YOURWEEEKTOKENHERE with a real token from , and restart the client:

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

npx downloads weeek-mcp on first launch and caches it. Cursor and Cline use the same mcpServers shape — see examples/cursor.mcp.json and examples/cline.mcp.json. Other env vars have safe defaults; override only what you need (see Configuration). If npx cannot find node (typical with nvm), see Troubleshooting; for a zero-dependency smoke test see docs/smoke.md.

examples/ lives on GitHub only — the npm tarball ships dist/ +

README.md + README.ru.md + LICENSE.

Tools

Ten read tools are exposed by default. All fifteen appear only under READ_ONLY=false (see Enabling write tools).

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Weeek: common questions

Is Weeek MCP server safe?
Mostly: it is graded B (83/100). Read the Weeek safety report
How do I install Weeek?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Weeek need an API key?
Yes. The registry entry asks for WEEEK_ACCESS_TOKEN.
Is Weeek maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v1.0.1.
How does Weeek compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.