$ loading_
Manage Weeek tasks, projects, and workspaces through natural language commands.
The available material is sparse, but the tool appears to wrap 71 Weeek API endpoints as MCP tools, which is a typical external-service integration. Open source is a positive sign, but missing documentation, undisclosed endpoints/auth details, and near-zero community adoption keep the overall assessment at caution.
The material claims integration with the Weeek API, yet lists no required keys/environment variables and provides no authentication details. If it actually accesses a user's Weeek tasks, projects, or workspace data, some form of account session or API credential is typically involved; the missing documentation makes credential sourcing, storage, and least-privilege boundaries unauditable.
The description explicitly says it wraps 71 Weeek API endpoints, so routine network egress to an external service should be expected for user requests and related business data. The material does not disclose the exact hosts/domains or data-flow scope, which reduces transparency, but there is no specific red flag here indicating exfiltration to unrelated or suspicious endpoints.
The system flags this tool as executes-code, meaning it has the normal MCP capability to run a local server/process. The provided material does not show requests for system privileges beyond its stated purpose, nor does it describe arbitrary shell/script execution, so this stays at caution rather than risk.
Based on the description, its primary data access surface is Weeek tasks, projects, and workspace resources, potentially acting on behalf of the user. The material does not explain local file access, cache locations, logging content, or permission scoping, so the access scope to remote business data may be broad, but there is no clear evidence of overreaching access to local machine data.
The project has a public source repository, which is a meaningful risk-reducing factor compared with closed-source tools. However, the missing README, unspecified license, zero-star adoption, and unknown maintenance status indicate weak maturity and limited trust signals. Overall, it is auditable but not yet well-established as a third-party component.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Weeek MCP Server" yet — see the docs or source repo.
In Weeek, create a task called "Complete homepage prototype review" in the "Mobile App Revamp" project, set the due date to this Friday, mark it high priority, and assign it to Zhang Lin.
Returns the created task details, including project, assignee, due date, and priority.
Summarize the current progress of the "Q3 Growth Plan" project in Weeek. List the number of completed, in-progress, and overdue tasks, and identify risk items.
Outputs a project progress overview with task status counts and key risk notes.
Check all unfinished tasks due this week in the Weeek workspace, group them by assignee, and generate a reminder summary for each person.
Returns overdue to-do lists grouped by assignee, plus reminder messages ready to send.
Manage WEEEK tasks, projects, boards, and time tracking via API.
Manage OpenProject projects, work packages, activities, and wiki pages through AI.
Manage files, monitor systems, keep notes, and fetch weather via MCP.
Manage Wrike tasks, projects, and workflows with natural language.
Connect to When2Work to check schedules, shifts, time off, and reports.
Let AI manage ClickUp tasks, comments, time tracking, and documents.