Connect Wekan to external systems via REST API

The Wekan MCP Server (built by namar0x0309 at GoAIX) gives AI agents seven tools to interact with a Wekan Kanban board: listBoards (list all boards accessible to the authenticated user), listLists (list all lists within a board), listSwimlanes (list all swimlanes in a board, used for organizing cards vertically), listCards (list all cards in a specific board and list), createCard (create a new card, with a required title and optional description, swimlane assignment, ISO 8601 due date, team-member IDs, and label IDs), moveCard (move a card to another list or swimlane within the same board), and commentCard (add a comment to an existing card). The project ships setup scripts that automatically generate a Wekan API token and write it into your environment configuration.

Use this connector when an agent needs to read and manage Wekan boards - listing boards, lists, swimlanes, and cards, creating and moving cards, or commenting on them - as part of a workflow. It is scoped to these seven operations only: there's no support here for deleting cards, managing labels or swimlanes themselves, board creation, or any Wekan feature beyond the listed tools, so it's not a fit if your workflow needs broader Wekan administration.

createCard takes a required title plus optional description, swimlane assignment, an ISO 8601 due date, an array of team-member user IDs, and an array of label IDs. moveCard takes a target list or swimlane within the same board. commentCard takes the card and comment text. The list* tools (listBoards, listLists, listSwimlanes, listCards) each return the matching boards, lists, swimlanes, or cards for a given board, and where relevant list, identifier. For development, the server integrates with the MCP Inspector (npm run inspect, or npm run inspect:watch for automatic rebuilding), configured via mcp-inspector-config.json, and ships two Node test scripts - test-auth.js to verify the token is working, and test-all-methods.js to exercise every available method.

Authentication runs against a Wekan instance via either a pre-generated WEKAN_API_TOKEN or a WEKAN_USERNAME/WEKAN_PASSWORD pair that generates a fresh token on each request; configuration lives in a .env file (WEKAN_BASE_URL, plus token, username, password, user ID, and token-expiry fields). Generate the token automatically by running the platform's script - get-wekan-token.ps1 on Windows (PowerShell) or get-wekan-token.sh on Linux/macOS - which prompts for the Wekan endpoint, username, and password, then creates or updates .env with the resulting token and config; or configure manually by copying .env.example to .env and filling in your Wekan instance details and token. Its own token-generation command for Linux/macOS, quoted verbatim:

./get-wekan-token.sh

Developers wiring an AI agent into an existing Wekan board for card and board-list visibility and lightweight card management - creating, moving, and commenting on cards - without building the Wekan API integration and token handling themselves.