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. It has been installed 0 times through Conduid.
The repository has 3 stars and 7 forks, with the last commit 10 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx 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.
Ask AI
Ask AI about Wekan
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !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.
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_USER_ID: Your Wekan user IDWEKAN_TOKEN_EXPIRES: Token expiration date
Testing
You can test your configuration by running:
node test-auth.js
This will verify that your API token is working correctly.
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 mirrored from the source repository 4 months ago. The original is authoritative.