Wekan MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEKAN_USER_ID | Yes | Your Wekan user ID | |
| WEKAN_BASE_URL | Yes | Your Wekan instance URL | |
| WEKAN_API_TOKEN | Yes | Generated API token for authentication | |
| WEKAN_TOKEN_EXPIRES | Yes | Token expiration date |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listBoardsA | List accessible Wekan boards |
| listListsC | List lists in a board |
| listSwimlanesC | List swimlanes in a board |
| listCardsC | List cards in a board+list |
| createCardD | Create a card |
| moveCardC | Move a card to another list or swimlane |
| commentCardC | Add a comment to a card |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: commenting, creating, listing different entities, and moving cards. No two tools have overlapping responsibilities.
All tools follow a consistent verb_noun pattern (commentCard, createCard, listBoards, etc.) with clear, predictable naming.
7 tools cover the core functionalities without being excessive or insufficient for a board management server.
Missing essential CRUD operations such as update or delete for cards and boards, and no tools for creating/editing lists or swimlanes, leaving significant gaps.