Skip to main content
Glama
Sign In
Kaiten MCP

Kaiten MCP

by 2chevskii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Kaiten MCP

No user-submitted related servers found.

    Related Servers

    • kaiten-mcp

      Amico1285
      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
      98 npm
      MIT

    • Kanban MCP Server

      rikamalov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to work a self-hosted kanban board as first-class users, exposing eleven kanban_* tools over a stateless Streamable HTTP endpoint for listing projects, stages, members and custom fields, and for creating, updating, moving and deleting tasks. Authenticates with bearer-token scopes so read-only or write access can be granted per agent, with every mutation audited.
      4
      MIT

    • ClickDown

      amscotti
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.
      231 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.1/5.0

    Scored across 51 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets, helped by detailed descriptions that clarify boundaries (e.g., card tags vs. workspace tags, comments vs. checklist items, archive vs. delete). There are many adjacent card sub-resource operations, so a few pairs such as list_card_tags/list_tags or remove/delete variants could still be confused at a glance, but the descriptions usually disambiguate.

    Naming Consistency4/5

    The dominant pattern is kaiten_verb_noun with snake_case (list_spaces, get_card, create_checklist, update_comment), applied consistently across most of the surface. Minor deviations exist in deletion verbs, mixing remove_ and delete_ (e.g., remove_card_tag vs. delete_checklist, remove_card_external_link vs. delete_comment), which slightly weakens predictability.

    Tool Count2/5

    At 51 tools, the surface is far above the typical well-scoped range and is likely to overwhelm an agent's selection process, especially with many narrow read-only property and directory lookup tools. While Kaiten is broad, a number of these operations could reasonably be consolidated into fewer parameterized tools.

    Completeness4/5

    The task/card domain is well covered: cards support create, read, update, move, archive/restore, delete, search, members, tags, comments, checklists, checklist items, external links, properties, and parent/child links. Gaps are mostly administrative or peripheral, such as creating boards/columns/lanes/spaces and managing custom property definitions, which are explicitly read-only and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources