Weeek MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add weeek-mcp -- npx -y weeek-mcp

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

[mcp_servers.weeek-mcp]
command = "npx"
args = ["-y", "weeek-mcp"]

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

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

This one needs environment variables set before it will start: WEEEK_ACCESS_TOKEN (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.). The author declared them in the registry entry; get the values from the project itself.