io.github.YOLKINS/weeek-mcp

io.github.YOLKINS/weeek-mcp

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

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "weeek-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "weeek-mcp@1.0.1"
      ],
      "env": {
        "WEEEK_ACCESS_TOKEN": "<your WEEEK_ACCESS_TOKEN>",
        "READ_ONLY": "true",
        "WEEEK_BASE_URL": "https://api.weeek.net/public/v1",
        "WEEEK_TIMEOUT_MS": "30000",
        "MAX_RESPONSE_CHARS": "65536"
      }
    }
  }
}
Environment variables
  • WEEEK_ACCESS_TOKENrequiredsecretWeeek Public API v1 access token. Required — the server refuses to start without it.
  • READ_ONLYGate 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.
  • WEEEK_BASE_URLOverride the Weeek API base URL. Defaults to the public v1 endpoint.
  • WEEEK_TIMEOUT_MSPer-request timeout in milliseconds.
  • MAX_RESPONSE_CHARSUpper bound on the JSON length of a single tool response, protecting the agent's context window from unbounded list/detail payloads.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.1
Registry
active
Published
8/20/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that io.github.YOLKINS/weeek-mcp is listed here — it’s also the link we check for a free listing.

io.github.YOLKINS/weeek-mcp — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-yolkins-weeek-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.YOLKINS/weeek-mcp — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![io.github.YOLKINS/weeek-mcp — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-yolkins-weeek-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.