Back to Browse

Weeek MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

WEEEK tasks by name, not IDs — an MCP server

About

WEEEK tasks by name, not IDs — an MCP server

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-structured MCP server for WEEEK task management with solid security practices. Authentication is properly required for API calls, sensitive operations like file attachment and deletion are guarded with appropriate restrictions, and the codebase shows good input validation and error handling. Minor code quality observations exist around broad error catching and logging, but these do not constitute security vulnerabilities. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 2 high severity). Package verification found 1 issue.

7 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

What You'll Need

Set these up before or after installing:

WEEEK personal API token (WEEEK → Settings → API)Required

Environment variable: WEEEK_API_TOKEN

Override API base for self-hosted / regional hosts (default https://api.weeek.net/public/v1)Optional

Environment variable: WEEEK_API_BASE_URL

Per-request timeout in ms (default 30000)Optional

Environment variable: WEEEK_TIMEOUT_MS

Directory weeek_attach_file may read from (default: the server's working directory)Optional

Environment variable: WEEEK_ATTACH_DIR

Max attachable file size in bytes (default 10485760)Optional

Environment variable: WEEEK_ATTACH_MAX_BYTES

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-ilyaivanchikov-weeek-mcp-smart": {
      "env": {
        "WEEEK_API_TOKEN": "your-weeek-api-token-here",
        "WEEEK_ATTACH_DIR": "your-weeek-attach-dir-here",
        "WEEEK_TIMEOUT_MS": "your-weeek-timeout-ms-here",
        "WEEEK_API_BASE_URL": "your-weeek-api-base-url-here",
        "WEEEK_ATTACH_MAX_BYTES": "your-weeek-attach-max-bytes-here"
      },
      "args": [
        "-y",
        "weeek-mcp-smart"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

weeek-mcp-smart

npm version npm downloads CI node license

The only one-click WEEEK MCP server — it takes names, not IDs. Create a task in one call:

weeek_create_task({ title: "Ship v1", project: "Marketing",
                    column: "In Progress", assignee: "Ilya", due: "next friday" })

No list_projects → list_boards → list_columns → list_members dance first.

Install (Claude Code / Cursor)

claude mcp add weeek -s user -- npx -y weeek-mcp-smart
# then set WEEEK_API_TOKEN in the generated config

Install (Claude Desktop, one click)

⬇ Download the latest .mcpb, then open it in Claude Desktop (Settings → Extensions → install from file). You'll be prompted for your WEEEK API token — it's stored in your OS keychain.

All releases: https://github.com/IlyaIvanchikov/weeek-mcp/releases

Get a token

WEEEK → Settings → API → generate a personal token.

Configuration

Env varRequiredDefaultPurpose
WEEEK_API_TOKENto call toolsYour WEEEK personal API token. The server starts and lists its tools without it, but any tool call fails until it is set.
WEEEK_API_BASE_URLnohttps://api.weeek.net/public/v1Override for self-hosted / regional hosts.
WEEEK_TIMEOUT_MSno30000Per-request timeout.
WEEEK_ATTACH_DIRnothe server's working directoryDirectory weeek_attach_file may read from (see Safety).
WEEEK_ATTACH_MAX_BYTESno10485760 (10 MB)Max attachable file size.

Safety

This server is driven by an LLM that can read untrusted content (task text, web pages), so the two riskiest tools are guarded:

  • weeek_attach_file only reads files inside an allowed directory (its subfolders included). By default that's the server's working directory — so it works with no setup for local files, while paths outside it (/etc/passwd, ~/.ssh, .. traversal, symlinks that escape) are refused. Set WEEEK_ATTACH_DIR to point the jail somewhere specific or lock it down further. No special folder is required.
  • weeek_delete_task is permanent and requires an explicit confirm: true; to merely close a task use weeek_complete_task.

Tools

Reads: weeek_version, weeek_list_projects, weeek_list_tasks, weeek_get_task. Writes: weeek_create_task, weeek_create_tasks, weeek_update_task, weeek_move_task, weeek_complete_task, weeek_attach_file, weeek_delete_task.

Author

Ilya IvanchikovGitHub · LinkedIn · Telegram · Channel

Reviews

No reviews yet

Be the first to review this server!