vikunja-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIKUNJA_URL | Yes | Base URL of the Vikunja instance, without /api/v1. | |
| VIKUNJA_TOKEN | Yes | API token with read/write access to tasks and comments. Never written to disk by this server, never logged. | |
| VIKUNJA_PROJECT | No | Default project (id or title) for tools with an optional project parameter. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Lista los proyectos de Vikunja (id, título, archivado). |
| list_tasksA | Tareas de un proyecto (id o título; sin |
| get_taskD | Una tarea con su descripción completa (texto plano). |
| create_taskA | Crea una tarea en un proyecto (sin |
| update_taskA | Actualiza una tarea: |
| add_commentA | Añade un comentario a una tarea (p. ej. el commit o la versión que la cerró). |
| list_commentsB | Comentarios de una tarea, en orden. |
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 7 tools
Each tool targets a distinct resource-action combination: projects vs tasks vs comments, with list/get/create/update/comment operations clearly separated. There is no overlap or ambiguity between tools like list_tasks and get_task, which are standard list-detail pairs.
All tool names follow the consistent snake_case verb_noun pattern (list_, get_, create_, update_, add_). The verbs are simple and predictable, making the API easy to learn and navigate.
Seven tools is well-scoped for a project/task management integration. Each tool covers a necessary operation without redundancy or bloat, fitting comfortably in the ideal 3-15 tool range.
Core task lifecycle is covered well: create, get, update (including done state), plus comments (add/list). The main gap is the lack of a delete task tool, and projects are only listed, not created or updated, but these are minor for typical task management use.