Skip to main content
Glama
4nm1tsu

vikunja-mcp

by 4nm1tsu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vikunja-mcp

No user-submitted related servers found.

    Related Servers

    • Vikunja MCP Server

      Wosh-i
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Vikunja task management instances through natural language. Supports comprehensive project and task operations including CRUD, assignments, labels, comments, relations, and attachments.
      33
      16 npm
      2
      MIT

    • vikunja-mcp

      crosbyh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • vikunja-mcp

      dev-montyoh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with Vikunja task management through its REST API, supporting projects, tasks, comments, labels, assignees, and relations with field preservation.
      16 npm
      MIT

    • Vikunja MCP Server

      lindenlion
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects 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.
      16 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.3/5.0

    Scored across 17 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources