Skip to main content
Glama
GitHub Kanban MCP Server

GitHub Kanban MCP Server

🎯 GitHub Kanban MCP Server

License: MIT TypeScript Node.js npm

📋 Overview

GitHub Kanban MCP Server is a Model Context Protocol (MCP) server for managing GitHub issues in Kanban board format and streamlining LLM task management.

Related MCP server: GitHub MCP Server

🚀 Features

  • 🔄 Manage GitHub issues in Kanban format

  • 🤖 Automated Task Management with LLM

  • 📊 Visualize project progress

  • 🔗 Full integration with GitHub

  • 💬 Comments on tasks

📁 Project Structure

kanban-server/
├── src/                    # ソースコードディレクトリ
│   ├── handlers/          # リクエストハンドラー
│   │   ├── comment-handlers.ts  # コメント関連の処理
│   │   ├── issue-handlers.ts    # Issue関連の処理
│   │   ├── label-handlers.ts    # ラベル関連の処理
│   │   └── tool-handlers.ts     # ツールリクエストの処理
│   ├── schemas/           # 入力スキーマ定義
│   │   ├── comment-schemas.ts   # コメント関連のスキーマ
│   │   └── issue-schemas.ts     # Issue関連のスキーマ
│   ├── utils/             # ユーティリティ関数
│   │   ├── error-handler.ts     # エラー処理
│   │   └── exec.ts             # コマンド実行関連
│   ├── server.ts          # MCPサーバーの実装
│   └── types.ts           # 型定義
├── docs/                  # ドキュメント
│   └── v0.2.0/           # バージョン別ドキュメント
└── assets/               # アセットファイル

🛠️ Installation

Prerequisites

  • Node.js 18.x or higher

  • npm 9.x or higher

  • GitHub CLI (gh)

# パッケージのインストール
npm install @sunwood-ai-labs/github-kanban-mcp-server

# GitHub CLIの認証設定
gh auth login

⚙️ Settings

Add the following to your MCP config file:

{
  "mcpServers": {
    "github-kanban": {
      "command": "github-kanban-mcp-server"
    }
  }
}

🔧 Available Tools

1. list_issues

Gets a list of issues on the Kanban board.

Input parameters:

  • repo : GitHub repository name (required)

  • state : The state of the issue ('open', 'closed', 'all').

  • labels : An array of labels to filter by.

2. create_issue

Create a new issue.

Input parameters:

  • repo : GitHub repository name (required)

  • title : Title of the issue (required)

  • emoji : Emoji to be added at the beginning of the title

  • body : The body of the issue

  • labels : An array of labels

  • assignees : Array of users to assign

3. update_issue

Update an existing issue.

Input parameters:

  • repo : GitHub repository name (required)

  • issue_number : Issue number (required)

  • title : New title

  • emoji : Emoji to be added at the beginning of the title

  • body : new body

  • state : The new state ('open', 'closed').

  • labels : An array of new labels

  • assignees : Array of new assignments

4. add_comment

Add a comment to the task.

Input parameters:

  • repo : GitHub repository name (required)

  • issue_number : ID of the task (issue) (required)

  • body : Comment content (Markdown format supported) (required)

  • state : The state of the issue to change when commenting ('open', 'closed')

📝 License

MIT License - See the LICENSE file.

🤝 Contributions

  1. Fork this repository

  2. Create a feature branch ( git checkout -b feature/amazing-feature )

  3. Commit your changes ( git commit -m '✨ feat: 素晴らしい機能を追加' )

  4. Push to the branch ( git push origin feature/amazing-feature )

  5. Create a pull request

📮 Feedback

If you have any problems or suggestions, please create an issue .

Available Tools

4 tools
add_commentB

タスクにコメントを追加

Inputs: body (required), repo (required), issue_number (required), state.

create_issueC

新しいissueを作成します

Inputs: title (required), body, path, emoji, +2 more.

list_issuesC

カンバンボードのissue一覧を取得します

Inputs: path, state, labels.

update_issueC

既存のissueを更新します

Inputs: issue_number (required), body, path, emoji, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing, creating, updating, or commenting on issues. No two tools overlap in purpose, so an agent can clearly distinguish them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_issues, create_issue, update_issue, add_comment). The verbs are clear and predictable.

    Tool Count5/5

    With 4 tools, the server is tightly scoped to core Kanban board operations. Every tool serves a necessary function without redundancy or bloat.

    Completeness4/5

    The basic lifecycle of issues is covered (list, create, update, comment). Missing operations like deleting or archiving issues are a minor gap since GitHub issues are typically closed rather than deleted, but board-specific transitions are not explicitly exposed.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers