Weeek MCP Server
Python MCP server for WEEEK API v1: tasks, projects, boards, funnels, deals and contacts, with SSE mode for n8n
- 3 ★ on the repository
- Last commit
Broad access
Why this level
- Can delete users, projects, tasks and deals
- SSE mode exposes the workspace API over the network
Install
- Works in
- Services
Manual install
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt
cp env.example .env
python -m src.serverRun inside the cloned github.com/AlekMel/weeek-mcp-server repo after putting WEEEK_TOKEN in .env.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can delete users, projects, tasks and deals
- SSE mode exposes the workspace API over the network
This is third-party code. Review the repository files before installing.
What it does
The server wraps the whole public WEEEK API as MCP tools. Beyond tasks, projects, boards and columns, the agent gets the WEEEK CRM side: funnels, statuses, deals, organizations and contacts, plus tags, custom fields, portfolios and users. Most entities have full CRUD, including delete. It runs locally over stdio or in Docker over SSE with an access key, which lets n8n call the tools. Tokens are masked in logs and requests retry on failures.
Who it is for. For WEEEK teams who need full API access from an agent or from n8n automations.
Good fit when
- You need WEEEK deals, funnels and contacts, not just tasks
- You need to call WEEEK from n8n workflows via MCP
- You need to create tasks or projects in bulk
Not a fit when
- You want a one-click Claude Code install: the claude-weeek plugin is easier
- The agent must not have tools that delete users and projects
Example request
Find all urgent WEEEK tasks and show deals at the negotiation stageMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
WEEEK_TOKENrequired, secret- API token from WEEEK settings
TRANSPORT- stdio by default or sse for network access
MCP_API_KEYsecret- Access key for SSE endpoints, required in SSE mode
Limitations
There is no registry package; install from source with Python 3.10+ and run from the repository folder. The README clone link is a placeholder, so use this repository's URL. Requires a WEEEK API token. SSE mode requires MCP_API_KEY, and the port must not be exposed without a firewall and HTTPS. Last changes date from late 2025.
How to disable. Delete the weeek block from the MCP client config, and run docker-compose down for Docker. Delete the token in WEEEK settings.
FAQ
How does it differ from the claude-weeek plugin?
This server covers the whole API, including CRM and deletes, and supports SSE for n8n. The plugin is limited to tasks without deletes but installs from a marketplace and ships skills.
How do I connect to a remote server?
Run Docker with TRANSPORT=sse and MCP_API_KEY and point the client at http://host:3847/sse with an Authorization: Bearer header.
How is Weeek MCP Server different from the claude-weeek plugin?
It is a Python MCP server that wraps the whole public WEEEK API v1: tasks, projects, boards, columns and the CRM part: funnels, statuses, deals, organizations and contacts. An SSE mode for n8n is included.
How do I connect Weeek MCP to a remote server and n8n?
Run the server in SSE mode and set its address in the client or in an n8n node. For a local install: python -m venv venv, then pip install -r requirements.txt, with the WEEEK key set as an environment variable. It works with Claude Desktop and Cursor. Risk is high.
Discussion
No questions or reviews yet.
Related
All WEEEK toolsWeeek MCP server
weeek-mcp
A local MCP server for Weeek: projects, tasks and boards are read-only by default, writes are opt-in
A WEEEK MCP server built from the official OpenAPI spec: tasks, time tracking and the full CRM part with funnels and deals
WEEEK 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
An MCP server for Weeek: projects, boards, tasks and time tracking with reports right from Claude Code
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
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Weeek MCP Server (this entry) | no | API key | 3 | |
| WEEEK MCP by names, not IDs | no | API key | 3 | creates tasks by names, no IDs |
| 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 Russian README walks through install from source, getting a WEEEK token and configuring .env. It covers local run, Docker and Docker Compose, SSE mode with a key, and VPS deployment with firewall and nginx. A section shows calling tools from n8n. It includes Claude Desktop and Cursor configs for stdio and SSE and the full tool list by API area.