← Index

io.github.YOLKINS/weeek-mcp

io.github.YOLKINS/weeek-mcpv1.0.0Other

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

The current version, v1.0.0, was published to the official MCP registry on 2026-08-17. It is distributed as weeek-mcp on npm, filed under Other by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using io.github.YOLKINS/weeek-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-17).

Contracts can change after screening, with no version bump. The gate pins io.github.YOLKINS/weeek-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
WEEEK_ACCESS_TOKEN
requiredsecret

Weeek Public API v1 access token. Required — the server refuses to start without it.

READ_ONLY

Gate for the write tools. Defaults to 'true': a fresh install exposes only the ten read tools. Set to 'false' to additionally expose the five write tools (create/update/move/complete a task, set an MR link) — an explicit operator opt-in, never the default.

ENABLED_TOOLS

Optional comma-separated allowlist of tool names to register (still subject to READ_ONLY). Pair with READ_ONLY=false for a granular write rollout, e.g. 'weeek_complete_task'.

WEEEK_BASE_URL

Override the Weeek API base URL. Defaults to the public v1 endpoint.

WEEEK_TIMEOUT_MS

Per-request timeout in milliseconds.

MAX_RESPONSE_CHARS

Upper bound on the JSON length of a single tool response, protecting the agent's context window from unbounded list/detail payloads.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
10
installability
25
documentation
15
stability
10
Alternatives in Other