Loading ToolBench

Reading the current corpus…

vikunja-mcp MCP server · F · ToolBench

vikunja-mcp

Model Context Protocol server for Vikunja task management - Simplified architecture with enterprise-grade security and reliability

<=2025-11-25STDIO11 tools

36/100

Definition Quality37

Protocol Readiness32

SupportabilityNot measured-

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Vikunja MCP has 11 tools with mixed quality. Tools 1-3 (auth, tasks, projects) have detailed schemas and descriptions; tools 4-11 lack visible schema definitions in source. Naming follows verb_noun convention (vikunja_*). Task and project tools accept enums and structured parameters. However, parameter descriptions are sparse or missing for many fields (e.g., 'sessionId' in tasks/projects unexplained). Output schemas are not documented. Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Batch operations present but composition could be tighter.

Tools (11)

vikunja_authread only50/100

Authenticate with Vikunja server using API token or JWT

vikunja_batch_importwriteauth35/100

Batch import tasks from external sources

vikunja_exportread onlyauth35/100

Export tasks and projects to various formats

vikunja_filterswriteauth35/100

Save, manage, and apply task filters

vikunja_labelswriteauth35/100

Manage labels for organizing and categorizing tasks

vikunja_projectswriteauthsource verified72/100

Manage projects with full CRUD operations, hierarchy management, and sharing capabilities

vikunja_taskswriteauthsource verified72/100

Manage tasks with comprehensive operations (create, update, delete, list, assign, attach files, comment, bulk operations)

vikunja_teams

Issues (5)

CRITICALtool-definition ↗

Tools 4-11 (labels, teams, users, filters, templates, webhooks, batch_import, export) have no visible input schemas in source code.

vikunja_labelsvikunja_teamsvikunja_usersvikunja_filtersvikunja_templatesvikunja_webhooksvikunja_batch_importvikunja_export

HIGHtool-description ↗

Parameter 'sessionId' appears in tasks and projects tools but is never explained in descriptions. LLMs cannot infer its purpose or when to provide it. Violates pattern:tool-description requirement that every parameter needs a description.

vikunja_tasksvikunja_projects

HIGHtool ↗

No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., task_id after create). Violates pattern:tool requirement for documented return types.

vikunja_authvikunja_tasksvikunja_projectsvikunja_labelsvikunja_teams

Recommendations

Add complete input schemas to tools 4-11 (labels, teams, users, filters, templates, webhooks, batch_import, export). Currently only tools 1-3 have visible schemas.
Document output schemas for all tools. Specify which fields are returned, their types, and which IDs/references are included for chaining (e.g., task_id after create_task).
Add descriptions to all parameters, especially 'sessionId' in tasks/projects. Explain what each parameter controls, its valid range/format, and when it is required.
Implement tool annotations: mark read-only tools (vikunja_auth, vikunja_export) with readOnlyHint=true; mark destructive tools (delete operations in tasks/projects) with destructiveHint=true; mark idempotent operations with idempotentHint=true.
Enhance error messages with recovery guidance. Instead of 'Task not found', return 'Task not found. Try list_tasks() to find the correct task ID.' This guides LLM retry logic.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

36/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	36	<=2025-11-25	v2