Skip to main content
Glama
shichao402

vikunja-mcp

by shichao402
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
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
      18 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.
      18 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.
      18 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.9/5.0

    Scored across 180 tools

    Disambiguation1/5

    The tool set contains extensive overlap: curated tools like vikunja_get_project and vikunja_delete_task duplicate raw proxies such as vk_get_projects_25ac8903752b and vk_delete_tasks_88ea47d49817. Many raw proxies have generic names with random hex suffixes (e.g., vk_get_projects_*), and placeholders like vk_get_kind_* make it impossible to distinguish purposes. Agents will struggle to select the correct tool among dozens of near-identical options.

    Naming Consistency1/5

    Naming follows no uniform pattern: there is a mix of vikunja_* (verb_noun) and vk_* (http_verb_entity_randomhash) prefixes, with some tools using different verbs (get/delete/put/post) and inconsistent object ordering. The random hash suffixes on raw proxies make names unpredictable and hard to memorize. The overall style is chaotic and lacks any consistent convention.

    Tool Count1/5

    With 180 tools, this server is drastically over-scoped for an MCP integration. Even if the raw proxies are auto-generated, exposing every endpoint as a separate tool creates overwhelming selection burden and token bloat. A well-designed MCP server would typically expose 10-20 curated tools, not hundreds of raw HTTP proxies.

    Completeness4/5

    The sheer number of raw proxies means nearly every Vikunja API endpoint is represented, covering projects, tasks, labels, comments, attachments, teams, users, webhooks, subscriptions, and migrations. However, the curated subset lacks some high-level CRUD operations (e.g., update/delete labels or comments) which forces agents to use the obscure raw proxies. The domain is broadly covered but not cohesively organized.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources