Skip to main content
Glama

Related Servers

Alternatives to kaiten-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Kaiten project management through its REST API. Enables managing spaces, boards, cards, comments, checklists, tags, and time logs.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Kaiten project management, providing 63 tools for managing cards, comments, checklists, time tracking, and more. Enables AI assistants to interact with Kaiten workspaces through natural language.
      63
      43 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for interacting with Kaiten (kaiten.ru) project management. Supports listing, moving tasks, setting responsible persons, and adding comments via natural language.
      7
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating Kaiten API with Claude Desktop, enabling management of cards, comments, spaces, and boards with advanced features like verbosity control, response format selection, and auto-truncation.
      5 npm
      32
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server and CLI tool for interacting with Kaiten project management API, optimized for token efficiency. Enables AI assistants to search, create, update, and manage tasks with minimal token usage.
      43 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (tags, members, external links, comments, checklists, time logs, planning views). There is mild overlap between kaiten_search_cards, kaiten_today_tasks, kaiten_overdue_cards and kaiten_plan_day, and kaiten_move_card / kaiten_archive_card are wrappers over kaiten_update_card, but the descriptions make the boundaries understandable.

    Naming Consistency4/5

    Consistent kaiten_ prefix with verb_noun structure throughout, and the remove/delete split appears semantic (remove = association like tag/member/link, delete = owned resource like card/comment/checklist item). Minor deviation: card sub-resources put 'card' mid-name (kaiten_add_card_external_link, kaiten_list_card_external_links) while others are verb_resource (kaiten_list_tags), giving slightly inconsistent word order.

    Tool Count2/5

    40 tools is well beyond the comfortable range and includes many near-duplicate CRUD variants across sub-resources. Several could be consolidated (move_card/archive_card into update_card, per-resource list/get pairs), making the surface heavy for an agent to navigate.

    Completeness4/5

    Strong lifecycle coverage for the core domain: cards, comments, checklists and items, tags, members, external links, time logs, plus spaces/boards/columns/lanes/users and planning views. Gaps remain (no delete_checklist, no attachment handling, no board/space creation, no get-single-comment or list-members on a card), but they are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive