| name | wekan-mcp-connector |
| description | MCP connector for Wekan open-source Kanban – enables AI-powered board management, card automation, and workflow optimization through Claude |
| license | MIT |
| tags | ["product","kanban","mcp","wekan"] |
| difficulty | beginner |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Wekan MCP Connector
Overview
This skill enables Claude to interact with Wekan through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Wekan's REST API, allowing natural language control of Wekan operations, intelligent automation, and AI-powered assistance for Wekan workflows.
When to Use This Skill
- Card creation and movement via natural language
- Board template generation for common workflows
- Checklist automation and progress tracking
- Due date management and overdue alerts
- Label and swimlane organization
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Wekan │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Wekan operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/boards, /api/boards/:id/lists, /api/boards/:id/cards, /api/boards/:id/members
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "wekan-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Wekan resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/boards`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"wekan-mcp-connector": {
"command": "node",
"args": ["path/to/wekan-mcp-connector/index.js"],
"env": {
"WEKAN_API_KEY": "your-api-key",
"WEKAN_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Wekan API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Wekan API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Move all overdue cards to a 'Blocked' list and add a comment explaining the delay"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
