Wekan MCP Server — Unofficial Tasks & Boards API

Overview

This project implements an unofficial MCP (Model Context Protocol) server for Wekan, exposing a simple REST API to manage boards, lists, and cards (tasks). It sits between a Wekan instance and external tools — chatbots, automation pipelines, or integrations — translating REST calls into Wekan operations so other systems can create, read, update, and delete tasks programmatically.

The server is useful when you need programmatic access to Wekan without using the Wekan UI or when you want to connect LLMs and automation platforms to your task data via a stable REST surface. Because it is an unofficial implementation, it aims to be lightweight and easy to run locally or in containers while requiring only minimal configuration to point at an existing Wekan instance.

Features

• Full CRUD operations for boards, lists, and cards (tasks)
• Simple REST endpoints designed for integration with MCP-aware tools and bots
• Lightweight server suitable for local development or containerized deployment
• Configurable connection to your Wekan instance via environment variables
• Example scripts and cURL snippets for common tasks
• Unofficial implementation: use alongside official Wekan deployments

Installation / Configuration

Prerequisites:

• Node.js (16+ recommended)
• npm or yarn
• Access to a running Wekan instance (URL and API token or credentials)

Clone and install:

git clone https://github.com/namar0x0309/wekan-mcp.git
cd wekan-mcp
npm install

Create a .env file (example):

# .env
PORT=3000
WEKAN_URL=https://your-wekan.example.com
WEKAN_TOKEN=your_wekan_api_token_or_session
LOG_LEVEL=info

Start the server:

# development
npm start

# or using node directly
node src/index.js

Docker (optional):

# build
docker build -t wekan-mcp:latest .

# run
docker run -e WEKAN_URL=https://your-wekan.example.com \
  -e WEKAN_TOKEN=your_wekan_api_token_or_session \
  -p 3000:3000 \
  wekan-mcp:latest

Note: Replace WEKAN_TOKEN with a valid API token or session mechanism your Wekan deployment supports. Consult your Wekan instance documentation if you need to create or retrieve API credentials.

Available Resources

Below is a concise overview of common endpoints provided by the server. Check the repository for a full, up-to-date specification.

Authentication for these endpoints is typically handled via the configured WEKAN_TOKEN and any additional headers the server requires. See the repo README for exact header expectations.

Use Cases

1. Automated Sprint Board Creation

• Create a new board for each sprint and seed lists and cards via CI/CD.
• Example (create board):

curl -X POST http://localhost:3000/boards \
  -H "Content-Type: application/json" \
  -d '{"title":"Sprint 2026-05"}'

2. Chatbot-driven Task Management

• Integrate with an assistant that can create and update cards when asked: “Create a task to review PR #42 and put it in In Review.”
• Example (create card in board):

curl -X POST http://localhost:3000/boards/<boardId>/cards \
  -H "Content-Type: application/json" \
  -d '{"title":"Review PR #42","listId":"<todoListId>","description":"Check tests and code style."}'

3. Cross-tool Synchronization

• Synchronize issues from Git repositories into Wekan cards for project tracking or mirror board status back into other dashboards.

4. Cleanup Automation

• Periodic jobs to remove stale tasks or archive completed boards by calling DELETE or update endpoints.

Notes and Next Steps

• This server is unofficial; behavior depends on the Wekan instance and API surface. Test in a staging environment before production use.
• Inspect the GitHub repository (https://github.com/namar0x0309/wekan-mcp) for the latest patches, contributor guidance, and issue tracking.
• Extend or adapt the server for custom workflow fields, webhooks, or richer authentication as needed.