About Wekan
Wekan is an MCP server published by namar0x0309 in the Developer Tools category: unofficial MCP server for Wekan, providing all rest api functionality to add, edit, delete tasks and boards.
The repository has 6 stars and 11 forks, with the last commit 4 months ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/namar0x0309/wekan-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (7)
commentCardAdd a comment to a card
Parameters not published.
createCardCreate a card
Parameters not published.
listBoardsList accessible Wekan boards
Parameters not published.
listCardsList cards in a board+list
Parameters not published.
listListsList lists in a board
Parameters not published.
listSwimlanesList swimlanes in a board
Parameters not published.
moveCardMove a card to another list or swimlane
Parameters not published.
Ask AI
Ask AI about Wekan
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 8 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Wekan MCP Server
made by namar0x0309 with ❤️ at GoAIX

This project includes scripts to automatically generate Wekan API tokens and configure your environment.
Supported Agent Functionality
The Wekan MCP Server provides the following tools for AI agents to interact with Wekan:
Board Management
- listBoards - List all accessible Wekan boards available to the authenticated user
List Management
- listLists - List all lists within a specific board
Swimlane Management
- listSwimlanes - List all swimlanes in a board (used for organizing cards vertically)
Card Management
- listCards - List all cards in a specific board and list
- createCard - Create a new card with support for:
- Title (required)
- Description (optional)
- Swimlane assignment (optional)
- Due date (optional, ISO 8601 datetime format)
- Team members (optional, array of user IDs)
- Labels (optional, array of label IDs)
- moveCard - Move a card to another list or swimlane within the same board
Card Interaction
- commentCard - Add a comment to an existing card
Getting Started
Generate Wekan API Token
Run the appropriate script for your platform to generate your API token:
Windows (PowerShell):
./get-wekan-token.ps1
Linux/macOS (Bash):
./get-wekan-token.sh
The script will prompt you for:
- Wekan endpoint (e.g., https://wekan.namar0x0309.com)
- Username
- Password
After successful authentication, it will:
- Generate an API token
- Create or update the
.envfile with your token and configuration
Manual Configuration
If you prefer to configure manually, copy .env.example to .env and fill in your details:
cp .env.example .env
Then edit the .env file with your Wekan instance details and API token.
Environment Variables
The .env file contains:
WEKAN_BASE_URL: Your Wekan instance URLWEKAN_API_TOKEN: Generated API token for authenticationWEKAN_USERNAME: Your Wekan username (alternative to API token)WEKAN_PASSWORD: Your Wekan password (alternative to API token)WEKAN_USER_ID: Your Wekan user IDWEKAN_TOKEN_EXPIRES: Token expiration date
Note: You can authenticate using either:
WEKAN_API_TOKEN- Pre-generated token, orWEKAN_USERNAMEandWEKAN_PASSWORD- For automatic token generation on each request
Testing
You can test your configuration by running:
node test-auth.js
This will verify that your API token is working correctly.
You can also test all available methods:
node test-all-methods.js
Development
MCP Inspector
For development and debugging the MCP server, you can use the MCP Inspector:
npm run inspect
This will launch the MCP Inspector with the configuration from mcp-inspector-config.json.
For development with automatic rebuilding:
npm run inspect:watch
This will build the project and launch the inspector, automatically rebuilding when changes are detected.
README fetched from the repository 8 days ago. The original is authoritative.