Weeek-mcp Server

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

Packages and local setup

The published npm package is weeek-mcp, version 1.0.1. Its declared MCP transport is stdio.

The package declares WEEEK_ACCESS_TOKEN (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.0.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.