A
licenseC
qualityD
maintenanceEnables AI assistants to interact with Vikunja task management instances, providing full task, project, label, and user management capabilities.
17
254 npm
MIT
Vikunja MCP Server
by Wosh-i
Related Servers
Alternatives to Vikunja MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables to interact with Vikunja task management through its REST API, supporting projects, tasks, comments, labels, assignees, and relations with field preservation.45 npmMIT
- AlicenseCqualityFmaintenanceEnables AI assistants to interact with Vikunja task management instances, providing full task, project, label, team, user, and webhook management operations through subcommand-based tools.16254 npm109MIT
- AlicenseCqualityCmaintenanceEnables AI assistants to interact with Vikunja task management via ergonomic and raw REST tools for projects, tasks, labels, and comments.1005 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude to self-hosted Vikunja instances for conversational task and project management. Supports CRUD operations on projects and tasks, plus labels, comments, weekly reviews, calendar feeds, and task relations.45 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants like Claude to manage Vikunja tasks – view, add, complete, edit, and delete tasks through natural language commands via Vikunja's REST API.MIT
TDQS
B3.3/5.0
Scored across 33 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity. Tools are precisely scoped to specific actions on specific resources (e.g., add_task_assignee vs. remove_task_assignee, create_task vs. update_task vs. delete_task). The descriptions reinforce this clarity, making misselection unlikely.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_project, list_tasks, update_task). All names use snake_case uniformly, and verbs are predictable (create, get, list, update, delete, add, remove, move, complete, reopen). This consistency enhances readability and predictability.
Tool Count3/5
With 33 tools, the count feels heavy for a task management server, bordering on excessive. While the tools cover many operations, a more streamlined set might improve usability. This is borderline, as it could overwhelm agents but is not extreme.
Completeness5/5
The tool surface is complete for the Vikunja task management domain. It covers full CRUD/lifecycle operations for projects, tasks, comments, attachments, labels, assignees, and relations, with no obvious gaps. Agents can perform all expected workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues