vikunja-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIKUNJA_URL | Yes | URL of your Vikunja instance | |
| VIKUNJA_API_TOKEN | Yes | API token for authentication |
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 |
|---|---|
| pingA | Test if the MCP server is working |
| projects_listC | List all projects the user has access to |
| projects_getA | Get a single project by ID |
| projects_createC | Create a new project |
| projects_updateB | Update an existing project |
| projects_deleteB | Delete a project |
| tasks_listB | List all tasks (optionally filtered by project) |
| tasks_getA | Get a single task by ID |
| tasks_createB | Create a new task in a project |
| tasks_updateB | Update an existing task |
| tasks_deleteC | Delete a task |
| labels_listB | List all labels the user has access to |
| labels_createB | Create a new label |
| labels_deleteB | Delete a label |
| task_labels_addB | Add a label to a task |
| task_labels_removeB | Remove a label from a task |
| task_comments_listB | List all comments on a task |
| task_comments_addB | Add a comment to a task |
| task_assignees_listB | List all assignees on a task |
| task_assignees_addB | Add an assignee to a task |
| task_assignees_removeB | Remove an assignee from a task |
| task_relations_addB | Create a relation between two tasks |
| task_relations_removeB | Remove a relation between two tasks |
| project_views_listB | List all views for a project |
| buckets_listA | List all kanban buckets for a project view |
| buckets_createB | Create a new kanban bucket |
| buckets_deleteB | Delete a kanban bucket |
| task_move_to_bucketB | Move a task to a different kanban bucket |
| teams_listB | List all teams the user belongs to |
| users_searchA | Search for users by username, name, or email |
| notifications_listB | List all notifications for the current user |
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 31 tools
Each tool addresses a distinct resource or action (e.g., projects, tasks, buckets, labels, notifications, teams, users). Even within tasks, sub-tools like assignees, comments, labels, and relations are clearly separated, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., buckets_create, projects_list, task_assignees_add). The convention is uniform across all 31 tools, with no mixing of camelCase or other styles.
The 31 tools cover a broad project management domain (projects, tasks, buckets, labels, notifications, teams, users). While slightly above typical MCP server scopes, each tool addresses a distinct operation, justifying the count.
CRUD operations are present for projects, tasks, labels, and buckets. Additional operations like moving tasks, managing assignees, comments, labels, and relations are included. Minor gaps exist (e.g., no comment update/delete, no notification management beyond listing), but core workflows are covered.