weeek-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@weeek-mcpshow me my open tasks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
weeek-mcp
Read-only MCP server for the Weeek Public API. Use it from Cursor or Claude Code to browse projects, search tasks, read attachments, and (with a browser session) load task comments.
Features
Can | Cannot |
Projects, boards, columns, tasks | Weeek Docs / Wiki (not in Public API) |
Search / filter tasks, my open tasks | Writes (not shipped; opt-in later) |
Members & tags | PDF/DOCX text extract (v1: URL / text files only) |
Attachments: images + txt/md/json/csv | |
Task comments via imported browser session | Comments are not in Public API |
“Documents” here means task attachments, not Weeek Docs.
Related MCP server: Weeek MCP Server
Requirements
Node.js ≥ 20
Weeek API token (Workspace settings → API)
Install
git clone https://github.com/prod-broke-again/weeek-mcp.git
cd weeek-mcp
npm install
npm run buildOptional: refresh vendored OpenAPI with npm run fetch:openapi, then npm run generate:dto.
Configuration
Copy .env.example and set at least WEEEK_API_TOKEN. Never commit .env or session cookies.
Variable | Required | Default | Notes |
| yes | — | Workspace API token |
| no | — | Used when tools omit |
| no | — | e.g. |
| no | all | Whitelist of project ids |
| no |
| Write tools not shipped in v1 |
| no |
| 8 MiB |
| no |
| Directory/project cache |
| no |
| Client-side rate limit |
| no |
| Logs go to stderr only |
| no |
| Public API |
| no |
| Private app API host |
| no |
| Browser session store |
| no | — | Optional cookie override |
| no | — | Needed if cookie string has no |
Cursor / Claude Code
Example Cursor MCP config (~/.cursor/mcp.json or project .cursor/mcp.json):
{
"mcpServers": {
"weeek": {
"command": "node",
"args": ["/absolute/path/to/weeek-mcp/dist/bin/weeek-mcp.js"],
"env": {
"WEEEK_API_TOKEN": "your-token",
"WEEEK_DEFAULT_PROJECT_ID": "2",
"WEEEK_READ_ONLY_PROJECTS": "2"
}
}
}
}More examples: examples/mcp.cursor.json, examples/mcp.claude.json.
Tools
weeek_context— start here (sessionComments: ready|missing)weeek_auth_status— session check + import instructionsweeek_session_import— paste session JSONweeek_list_projectsweeek_get_projectweeek_get_boardweeek_search_tasksweeek_my_tasksweeek_get_task— card + comments when session is readyweeek_get_task_comments— comments onlyweeek_get_task_treeweeek_read_attachmentweeek_list_membersweeek_list_tags
Typical flow: context → (auth_status / session_import if needed) → search_tasks → get_task → read_attachment.
Task comments (browser session)
Public API has no comments. The web app loads them from:
GET https://api.weeek.net/ws/{workspaceId}/tm/tasks/{taskId}?withSubtasks=1
with session cookies. weeek_session is HttpOnly, so document.cookie cannot see it.
Import once
Call
weeek_auth_status(or open a task viaweeek_get_task_comments).In https://app.weeek.net → DevTools → Network → open any task.
Find
api.weeek.net/ws/.../tm/tasks/...→ Request Headers → Cookie → copy the value.Console: paste the helper from
weeek_auth_status, then runweeekExportSession("PASTE_COOKIE_HERE")
(or pass workspace id as the second argument).Paste the JSON into chat / call
weeek_session_import.
Session is stored at ~/.weeek-mcp/session.json (Windows: %USERPROFILE%\.weeek-mcp\session.json).
Security: the cookie is a live login. Do not commit or share it. If leaked, log out of Weeek or rotate the password.
Development
npm test
npm run typecheck
npm run build
npm run dev # stdio MCP via tsxOpenAPI is vendored at openapi/weeek.json. Layout: domain → application → infrastructure → mcp.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server for accessing Productive.io API endpoints (projects, tasks, comments, todos), tailored for read-only operations, providing streamlined access to essential data while minimizing token consumptionLast updated18MIT
- Flicense-qualityDmaintenanceFull-featured MCP server integrating all 71 endpoints of the Weeek API as MCP tools for AI clients, enabling task, project, and workspace management via natural language.Last updated2
- AlicenseCqualityCmaintenanceMCP server for WEEEK Public API v1 enabling management of tasks, projects, boards, tags, custom fields, time tracking, and CRM entities.Last updated10046MIT
- Alicense-qualityDmaintenanceRead-only MCP server for Things 3 to retrieve completed tasks by date, weekly summaries, and project reports for analysis and reflection.Last updated32ISC
Related MCP Connectors
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
Read-only MCP server for the WebAssembly spec: instructions, types, sections, search, proposals.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prod-broke-again/weeek-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server