vikunja-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| LOG_LEVEL | No | Set log level (error, warn, info, debug) | info |
| VIKUNJA_URL | Yes | Vikunja instance URL (required) | |
| VIKUNJA_API_TOKEN | Yes | Authentication token (API token starting with tk_ or JWT token) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vikunja_authC | Manage authentication with Vikunja API (connect, status, refresh, disconnect) |
| vikunja_bucketA | Kanban buckets (columns/statuses): list a project's views, list a view's buckets, and MOVE a task into a bucket. Use this to move a task between kanban columns, e.g. Backlog -> Review -> Done. |
| vikunja_tasksD | Manage tasks with comprehensive operations (create, update, delete, list, assign, attach files, comment, bulk operations) |
| vikunja_task_crudC | Manage individual tasks: create, get, update, delete, list |
| vikunja_task_bulkC | Manage bulk task operations: create, update, delete multiple tasks |
| vikunja_task_assigneesC | Manage task assignments: assign users, unassign users, list assignees |
| vikunja_task_commentsC | Manage task comments: add a comment, or list a task's comments |
| vikunja_task_remindersC | Manage task reminders: add, remove, list reminders |
| vikunja_task_labelsC | Manage task labels: apply, remove, list labels |
| vikunja_task_relationsC | Manage task relationships: relate tasks, unrelate tasks, list relations |
| vikunja_projectsC | Manage projects with full CRUD operations, hierarchy management, and sharing capabilities |
| vikunja_labelsC | Manage task labels with full CRUD operations for organizing and categorizing tasks |
| vikunja_teamsC | Manage teams and team memberships for collaborative project management |
| vikunja_filtersC | Manage and build advanced filters for tasks and projects with validation |
| vikunja_templatesD | Manage task templates for creating consistent tasks and project structures |
| vikunja_webhooksC | Manage webhooks for integrating Vikunja events with external services |
| vikunja_batch_importB | Import tasks in bulk from CSV or JSON formats with error handling and dry-run support |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
The 'vikunja_tasks' tool description claims to handle all task operations, overlapping with many specialized tools like vikunja_task_crud, vikunja_task_assignees, vikunja_task_comments, etc. This creates significant ambiguity about which tool to use for task-related actions, leading to potential misselection.
All tools share the 'vikunja_' prefix, but the suffix naming is inconsistent: some use plain nouns (auth, filters, projects), while tasks have a mix of 'vikunja_tasks' and 'vikunja_task_*'. The plural 'tasks' vs singular 'task' adds inconsistency, though overall the pattern is still readable.
With 17 tools, the count is slightly above the typical 3-15 well-scoped range. The duplication due to the overlapping 'vikunja_tasks' tool makes the set feel heavier than necessary, but for a full-featured task management server, 17 tools could be justified if each had a distinct role.
The tool surface covers authentication, projects, tasks (with comments, labels, relations, reminders, bulk operations), teams, templates, webhooks, and filters. It addresses most lifecycle operations for the domain, though the redundancy suggests some consolidation could be possible.