Skip to main content
Glama

Related Servers

Alternatives to Kaiten MCP Tools

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
    • 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
      B
      quality
      B
      maintenance
      MCP-сервер для полного управления Kaiten из любого MCP-клиента. Предоставляет 36 инструментов для работы с пространствами, досками, карточками, комментариями, чек-листами, учётом времени, тегами, участниками, гибкими выборками и планированием дня.
      40
      317 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to manage Kanban projects and tasks over MCP, including creating and listing projects/tasks, setting prerequisites, moving/archiving/restoring/deleting/reordering tasks, tracking history, and accessing attachments. Actions affecting multiple tasks return confirmation requests before applying changes.
      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
      35 npm
      MIT

    TDQS

    B3/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and descriptions specify scope well. Minor overlap exists among card-listing tools (list_board_cards, list_space_cards, search_cards) and the time-tracking trio (get_user_timelogs, get_card_timelogs, get_timesheet), which could cause occasional misselection.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern (list_*, get_*, search_*, download_attachment). No mixed conventions or vague standalone verbs are present.

    Tool Count2/5

    37 tools is heavy for the apparent scope, and many are highly granular read endpoints (e.g., list_card_tags, list_card_members, list_card_blockers, list_card_external_links) that could be folded into composite card retrieval. The set is broad but fragmented, making it harder to navigate.

    Completeness2/5

    The surface is entirely read-only: there are no create, update, or delete operations for cards, comments, documents, boards, or time logs. Read coverage is extensive, but the absence of write operations leaves significant lifecycle gaps that would cause agent failures on mutation tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues