Vikunja MCP Server
@democratize-technology
Model Context Protocol server for Vikunja task management. Enables AI assistants to interact with Vikunja instances via MCP.
Overview
What is Vikunja MCP Server?
A Model Context Protocol (MCP) server that enables AI assistants to interact with Vikunja task management instances. It provides subcommand-based tools for full task, project, label, team, user, and webhook management.
How to use Vikunja MCP Server?
Install via npx -y @democratize-technology/vikunja-mcp or build locally, then configure environment variables VIKUNJA_URL and VIKUNJA_API_TOKEN (or JWT token) in your MCP client. Use subcommand tools like vikunja_tasks.create and vikunja_auth.connect after authentication.
Key features of Vikunja MCP Server
- Subcommand-based tools for intuitive AI interactions
- Full task, project, label, and team management
- Batch import tasks from CSV or JSON files
- Zod-based input validation and DoS protection
- Production‑ready retry logic with circuit breaker
- Automatic API token or JWT detection
Use cases of Vikunja MCP Server
- Automate task creation and updates via AI assistants
- Manage projects and labels through natural language commands
- Bulk import tasks from CSV/JSON files into Vikunja
- Retrieve and organize tasks with advanced filtering and sorting
FAQ from Vikunja MCP Server
What authentication methods are supported?
Supports API tokens (starting with tk_) for most operations and JWT tokens (starting with eyJ) for full access including user management and export. Token type is automatically detected.
What are the runtime requirements?
Requires Node.js 20+ (LTS only) and an existing Vikunja instance with API access.
How do I obtain an API token?
Go to Vikunja Settings → API Tokens → Create new token. The token format starts with tk_.
Are there rate limits or memory protections?
Yes, the server includes configurable rate limiting against DoS attacks and memory protection with pagination limits and usage monitoring.
Can I use JWT tokens for user management?
Yes, JWT tokens enable access to user‑specific endpoints (profile, settings, export) which are not available with API tokens.