Skip to main content
Glama
ViktorOgnev

kaiten-mcp

by ViktorOgnev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

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

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

    C2.9/5.0

    Scored across 246 tools

    Disambiguation2/5

    With 246 tools, several near-duplicates blur boundaries: list_cards vs list_all_cards, get_space_activity vs get_all_space_activity, and chart_control vs chart_cycle_time vs chart_lead_time. While many resource areas are distinct, the sheer volume plus overlapping bulk/all variants makes reliable tool selection difficult.

    Naming Consistency4/5

    The vast majority follow a consistent kaiten_verb_noun pattern (list, get, create, update, delete, add, remove). Minor deviations like kaiten_chart_cfd and kaiten_batch_add_sd_org_users break the pattern slightly, but overall naming is predictable.

    Tool Count1/5

    246 tools is an extreme mismatch for an MCP server; even a full platform API is better grouped into multiple focused servers. The count alone makes the toolset impractical for an agent to navigate and select from efficiently.

    Completeness4/5

    The surface is very comprehensive, covering CRUD-style operations for spaces, boards, cards, documents, checklists, custom properties, Service Desk, SLA policies, webhooks, and more. Minor gaps exist, such as missing single-get endpoints for some resources and a few operations documented as likely returning 405.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources