Skip to main content
Glama
zurdi15

vikunja-mcp

by zurdi15
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vikunja-mcp

No user-submitted related servers found.

    Related Servers

    • vikunja-mcp

      semaputnik
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to interact with a Vikunja instance through tools for listing, creating, updating, and removing tasks, projects, and labels. It deliberately avoids permanent task deletion, using a configurable label for soft removal instead.
      11
      MIT

    • vikunja-mcp

      mbogner
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges MCP clients to a self-hosted Vikunja instance, exposing tools for managing projects, tasks, labels, and comments.
      48 npm
      MIT

    • 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
      48 npm
      2
      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.
      48 npm
      MIT

    • vikunja-mcp

      0xK3vin
      A
      license
      B
      quality
      D
      maintenance
      Connect your AI assistant to Vikunja, the open-source task manager. This MCP server lets you manage projects, tasks, kanban boards, and more—just by asking.
      31
      49 npm
      15
      MIT
    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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources