Kanban vs Gitscrum Core MCP
A side-by-side look at the Kanban and Gitscrum Core MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kanban for product management work as a local process; choose Gitscrum Core MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kanban when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
task_add, task_list, task_move.
Choose Gitscrum Core MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
task, sprint, workspace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 17 | 29 |
| Full listing | View Kanban | View Gitscrum Core MCP |
Tools & capabilities
Kanban tools 17
task_addAdd a task: title plus optional project, column, due date, estimate, priority, tags and notes. A new project name creates its board; a partial name that matches exactly one existing project is used as that project.task_listTable of tasks, filtered by project, column, tag, `due_before` or `overdue`. Finished tasks are hidden unless you ask for them. Prints 200 rows by default and says how many more there are; raise it with `limit` (max 2,000).task_moveMove a task to another column on its board.task_updateChange any field: title, notes, due (`none` clears it), estimate, priority, tags, column or project.task_doneMark a task done: it moves to the done column and is stamped with the time.task_deleteDelete a task. The id is never reused.task_searchFind tasks by text in the title, notes, tags or id.boardColumn-by-column summary of one board: tasks, estimate total, actual total, overdue count.task_start_timerReturn the exact arguments to pass to the time-tracker server's `timer_start` for this task, and record the link on the task.task_log_timeAdd real minutes worked to a task, so estimate and actual can be compared.project_listEvery board with open and done counts, remaining estimate and overdue count.project_deleteDelete an empty board and free its project slot. A board that still holds tasks, open or done, is refused with a task named; clear them with `task_delete` first.- +5 more on the listing page
Gitscrum Core MCP tools 29
task[tasks](docs/tools/tasks.md)sprint[sprints](docs/tools/sprints.md)workspace[projects](docs/tools/projects.md)project[projects](docs/tools/projects.md)time[time-tracking](docs/tools/time-tracking.md)user_story[user-stories](docs/tools/user-stories.md)epic[epics](docs/tools/epics.md)label[labels](docs/tools/labels.md)task_type[task-types](docs/tools/task-types.md)workflow[workflows](docs/tools/workflows.md)discussion[discussions](docs/tools/discussions.md)comment[comments](docs/tools/comments.md)- +17 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kanban
{
"mcpServers": {
"kanban": {
"command": "npx",
"args": [
"-y",
"@theluckystrike/mcp-kanban"
]
}
}
}
Gitscrum Core MCP
{
"mcpServers": {
"mcp-93": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
]
}
}
}
Frequently asked questions
Kanban is categorized under Product Management and uses a local stdio subprocess. Gitscrum Core MCP belongs to Product Management and uses a local stdio subprocess. Pick Kanban for product management work and Gitscrum Core MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kanban has no declared pricing — check the project's own site. Gitscrum Core MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kanban and mcp-93 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kanban has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Gitscrum Core MCP has 57/100 (Good) with 0 views, 0 installs and 5 GitHub stars.