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
      Not graded
      quality
      B
      maintenance
      MCP-сервер для полного управления Kaiten из любого MCP-клиента. Предоставляет 36 инструментов для работы с пространствами, досками, карточками, комментариями, чек-листами, учётом времени, тегами, участниками, гибкими выборками и планированием дня.
      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 34 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: card reading vs searching vs container-based listing, card history, subtasks, comments, checklist, members, blockers, links, tags, spaces, boards, columns, lanes, users, roles, tags, custom properties, sprints, time logs, and attachments. The few potentially overlapping tools (e.g., search_cards, list_space_cards, list_board_cards) are clearly scoped by route and container, so misselection is unlikely.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_card, search_cards, list_space_cards, list_card_members, download_attachment, etc. There is no mixing of conventions or vague verb styles.

    Tool Count2/5

    With 34 tools, the set is heavy relative to typical MCP servers and the read-only scope. Many list_* tools are highly granular for individual card sub-resources, which bloats the surface beyond what an agent can comfortably navigate. This exceeds the 25+ threshold where tool count is considered too many.

    Completeness2/5

    The tool surface is entirely read-oriented: no create, update, delete, or write operations for cards, comments, checklists, members, blockers, tags, boards, users, time logs, or attachments. For a project management domain like Kaiten, this leaves significant lifecycle gaps that will cause agent failures for any task requiring modification.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues