Vikunja MCP Server

Task planning in Vikunja can move between individual edits and batch work through this MCP integration. Assistants can search and filter tasks across projects, adjust due dates and priorities, set recurrence, manage assignees, and add comments or reminders. Task relationships cover subtasks, dependencies and related work. Projects can be created, retrieved, edited or deleted, while labels organize tasks and webhooks support project automation. Bulk actions create, update or delete tasks; CSV and JSON imports can resolve label names and usernames, and a dry run validates data without adding tasks.

Access starts with authentication to a Vikunja instance, supplied through environment configuration or a connection tool. API tokens cover the main task, project, label, team and webhook workflows, but user-specific endpoints and export require JWT authentication. JWTs expire, so replacement tokens are needed when they do. Team retrieval, updates and membership operations remain constrained by the Vikunja API. The server communicates over stdio and runs on Node.js 20 or later, restricted to LTS versions. Input checks cover dates, identifiers and hexadecimal colors, alongside configurable rate limits and pagination limits.