Skip to main content
Glama
theYahia

@theyahia/kaiten-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @theyahia/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
      14 npm
      MIT

    • ClickDown

      amscotti
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.
      85 npm
      MIT

    • kaiten-mcp

      DVZak
      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
    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

    B3.3/5.0

    Scored across 63 tools

    Disambiguation5/5

    Every tool targets a distinct resource or subresource (spaces, boards, columns, lanes, cards, members, tags, blockers, checklists, comments, sprints, custom properties), and the verb prefixes clearly separate read from mutation operations. An agent should rarely confuse one tool with another, even within the dense card subresource family.

    Naming Consistency4/5

    The set largely follows a snake_case verb_noun pattern (list_spaces, create_board, update_card), and card subresources consistently use list_card_* / add_card_* / remove_card_*. Minor inconsistencies like block_card/unblock_card instead of create/delete_card_blocker, and delete_comment vs remove_* for other subresources, prevent a perfect score.

    Tool Count1/5

    With 63 exposed operations, the tool surface is far beyond the 3–15 range that makes a coherent MCP server easy for an agent to navigate. Even though the tools are logically grouped by Kaiten's domain, the raw API-style granularity creates an extreme selection burden and warrants a low score.

    Completeness4/5

    The core lifecycle is well covered: spaces, boards, columns, lanes, cards, comments, checklists, members, tags, blockers, and external links all have create/read/update/delete or equivalent operations. Minor gaps remain—no get_column/get_lane, no workspace-level tag or sprint CRUD, and custom properties are read-only—but agents can usually work around them via list and board endpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources