WEEEK tasks and CRM by name, not IDs — an MCP server covering the whole public API
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.
claude mcp add weeek -s user -- npx -y weeek-mcp-smart
# then set WEEEK_API_TOKEN in the generated config
⬇ 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
WEEEK → Settings → API → generate a personal token.
| Env var | Required | Default | Purpose |
|---|---|---|---|
WEEEK_API_TOKEN | to call tools | — | Your 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_URL | no | https://api.weeek.net/public/v1 | Override for self-hosted / regional hosts. |
WEEEK_TIMEOUT_MS | no | 30000 | Per-request timeout. |
WEEEK_ATTACH_DIR | no | the server's working directory | Directory weeek_attach_file may read from (see Safety). |
WEEEK_ATTACH_MAX_BYTES | no | 10485760 (10 MB) | Max attachable file size. |
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.weeek_get_attachment returns the image for an attachment WEEEK hosts itself, so a task specified in screenshots can be read rather than guessed at. It downloads bytes only when the attachment's service is weeek; an attachment parked in Google Drive/Dropbox/OneDrive/Box comes back as metadata with its URL instead. The download sends no token at all: WEEEK hands out a pre-signed one-hour URL that redirects to its storage bucket, and the server follows exactly one redirect, only to https, with no credentials on either hop. Non-images return metadata only, and anything over WEEEK_ATTACH_MAX_BYTES is refused rather than truncated.Reads: weeek_version, weeek_list_projects, weeek_list_tasks, weeek_get_task, weeek_list_members, weeek_get_attachment.
Writes: weeek_create_task, weeek_create_tasks, weeek_update_task, weeek_move_task, weeek_complete_task, weeek_attach_file, weeek_delete_task.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y weeek-mcp-smartMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ilyaivanchikov-weeek-mcp-smart": {
"command": "npx",
"args": [
"-y",
"weeek-mcp-smart"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceWEEEK (smart) works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.