GitLab Kanban MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URL | No | Your GitLab instance URL | https://gitlab.com |
| GITLAB_TOKEN | Yes | Your GitLab personal access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tasksC | プロジェクトのカンバンボードのタスク一覧を取得 |
| create_taskC | カンバンボードに新しいタスクを作成 |
| update_taskC | カンバンボードのタスクを更新 |
| delete_taskC | カンバンボードのタスクを削除 |
| add_commentC | タスクにコメントを追加 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: list_tasks retrieves tasks, create_task adds new ones, update_task modifies existing tasks, delete_task removes them, and add_comment adds comments to tasks. There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_tasks, create_task, update_task). The naming is uniform and predictable across all five tools, enhancing readability and usability.
With 5 tools, this server is well-scoped for managing tasks in a GitLab Kanban board. Each tool serves a distinct and essential function (CRUD operations plus commenting), and there are no extraneous or missing tools for the domain.
The tool set provides complete CRUD coverage for tasks (list, create, update, delete) and includes an additional operation for adding comments. This covers the core lifecycle of Kanban tasks without any obvious gaps, ensuring agents can handle all basic workflows.