Weeek MCP Server
Python MCP server for WEEEK API v1: tasks, projects, boards, funnels, deals and contacts, with SSE mode for n8n
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.
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 stageLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| WEEEK_TOKEN required, secret | API token from WEEEK settings |
| TRANSPORT | stdio by default or sse for network access |
| MCP_API_KEY secret | Access key for SSE endpoints, required in SSE mode |
Security check
- Can delete users, projects, tasks and deals
- SSE mode exposes the workspace API over the network
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.
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.
Related
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI
Anthropic's official plugins for knowledge work roles: sales, support, product, marketing, legal, finance, data and enterprise search