Skip to main content
Glama
sunblob

Vikunja MCP Server

by sunblob
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Vikunja MCP Server

No user-submitted related servers found.

    Related Servers

    • 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 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.
      18 npm
      -

    • vikunja-mcp

      skrimokst
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that exposes tasks in a Vikunja instance as typed tools for list, get, add, update, complete, and reopen operations, enabling natural language task management via Claude.
      7
      -

    • 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.
      18 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
      18 npm
      1
      MIT

    • 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
    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

    B3.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are clearly separated by resource (projects, tasks, labels) and action (list, get, create, update, complete). The only minor overlap is update_task vs complete_task for marking a task done, but the description explicitly redirects that use case.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_projects, get_task, create_label, etc.). There are no deviations or mixed conventions.

    Tool Count5/5

    With 10 tools, the set is well within the ideal 3-15 range and each tool maps to a distinct operation. It is focused without unnecessary redundancy.

    Completeness3/5

    Task management has create/get/update/complete but lacks delete_task. Projects and labels lack update and delete operations entirely, which are notable gaps for a complete task management surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources