WEEEK MCP by names, not IDs
weeek-mcp-smart
A WEEEK MCP server creates a task from project, column and assignee names in one call, no chain of lookups for their IDs
- 4 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Creates and changes tasks in the WEEEK workspace using a broadly scoped token
- The API token grants access to the whole workspace, not just tasks
Install
- Works in
- Services
Manual install
claude mcp add weeek -s user -- npx -y weeek-mcp-smartThe README's command; WEEEK_API_TOKEN is then set in the generated config.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates and changes tasks in the WEEEK workspace using a broadly scoped token
- The API token grants access to the whole workspace, not just tasks
This is third-party code. Review the repository files before installing.
What it does
Normally, creating a task via the WEEEK API means first looking up the project, board, column and assignee ids with four separate calls. This server accepts human names directly in one weeek_create_task call: project, column, assignee and a free-form due date like next friday, resolving them to the right ids itself. It installs as a regular npm package for Claude Code and Cursor, or as a one-click .mcpb extension for Claude Desktop, where the token is kept in the OS keychain rather than a plain-text config.
Who it is for. For people who want to create WEEEK tasks in one phrase without first figuring out numeric project and column ids.
Good fit when
- You want to create a task by project and column name rather than id
- You use Claude Desktop and want a one-click .mcpb install
- You want a due date in free form, like next friday
Not a fit when
- You need access to WEEEK's knowledge base or CRM parts, the server is focused on tasks
- You need full coverage of every WEEEK API operation rather than convenient task creation
Example request
Create a task Ship the release in the Marketing project, column In Progress, assignee Ilya, due next fridayMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
WEEEK_API_TOKENrequired, secret- A personal WEEEK token from the Settings → API section.
Limitations
The server is focused on tasks and creating them by name, not on full WEEEK API coverage. It needs a personal WEEEK API token from workspace settings.
How to disable. Remove the weeek server from your MCP client configuration, or remove the .mcpb extension in Claude Desktop via Settings → Extensions.
FAQ
How is this different from other WEEEK MCP servers?
The main selling point, per the author, is that a task is created from project, column and assignee names in one call, skipping the list_projects, list_boards, list_columns and list_members lookups.
Where is the token stored with the .mcpb install?
In the OS keychain, rather than a plain-text config file.
Discussion
No questions or reviews yet.
Related
All WEEEK toolsWEEEK MCP with a read/write split
weeek-mcp-server
A 12-tool WEEEK MCP server split into 7 read and 5 write tools, so an MCP client can auto-approve the safe ones
WEEEK CLI and MCP on Bun
Weeek CLI + MCP Server
A weeek CLI command and an MCP server for WEEEK in one Bun package: projects, boards, tasks and subtasks from a terminal or an agent
Weeek MCP server
weeek-mcp
A local MCP server for Weeek: projects, tasks and boards are read-only by default, writes are opt-in
Python MCP server for WEEEK API v1: tasks, projects, boards, funnels, deals and contacts, with SSE mode for n8n
WEEEK MCP with confirm-gated writes
weeek-mcp
A WEEEK MCP server that is read-only by default: tasks, attachments and comments via a browser session, writes are opt-in
An MCP server for Weeek: projects, boards, tasks and time tracking with reports right from Claude Code
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| WEEEK MCP by names, not IDs (this card) | no | API key | 4 | |
| Weeek MCP Server | no | API key | 2 | tasks, CRM and SSE for n8n |
| WEEEK MCP with a read/write split | no | API key | 1 | reads separate |
| WEEEK MCP with confirm-gated writes | no | API key | 0 | writes on request |
README in short
The English README pitches the server as the only one-click WEEEK MCP, where a task is created by names rather than ids, with a weeek_create_task example. It shows two install paths: npx for Claude Code and Cursor, and .mcpb for Claude Desktop with keychain token storage, plus an environment variable table.