The kanban board for open source maintainers
Maintainer time is the scarcest resource in open source. Kanboard turns the endless issue firehose into a triaged queue — and over MCP, AI agents can burn down the mechanical end of it while you review.
Sound familiar?
The issue tracker is a firehose, not a queue
Hundreds of open issues with no order. What's triaged, what's claimed, what's abandoned — impossible to see at a glance.
Mechanical work crowds out judgment work
Reproductions, dependency bumps, doc fixes — necessary toil that consumes the hours reviews and design decisions deserve.
Weekend-sized time slots
You maintain in stolen hours. Rebuilding 'where was I?' costs half of every session.
How Kanboard fits
A triage board
Columns like Triage, Accepted, In Progress, Done turn the firehose into a queue with a visible front.
MCP server
Agents pick up the mechanical tasks — write the repro, bump the dependency, draft the doc fix — and move them to Done for your review.
REST API
A small script syncs labeled GitHub issues onto the board, so triage happens once, in one place.
Flat pricing
Pro is $12/month flat, with unlimited projects so every repo you maintain gets its own triage board.
A week on the board
- 1
Sync or copy the issues worth doing onto the board; everything else stays in the tracker.
- 2
Order Accepted by impact; mark agent-friendly tasks in the title (e.g. a [mech] prefix).
- 3
Let an agent work the mechanical tasks over MCP during the week.
- 4
Spend your maintainer hours reviewing the Done column and doing the design work only you can do.
FAQ
Does Kanboard integrate with GitHub Issues?+
There's no built-in sync yet — maintainers use the REST API to mirror labeled issues onto the board with a short script or a scheduled Action.
How much does Kanboard cost for open source work?+
Pro is $12/month flat and includes unlimited projects plus the MCP server and REST API for agent workflows.
What agent tasks work best for OSS maintenance?+
Bounded, verifiable ones: reproduce this bug, upgrade this dependency and fix breakage, add tests for this module, draft docs for this API. Put acceptance criteria in the task description.
Can co-maintainers share the board?+
Boards are single-account today; teams typically run a shared maintenance account or coordinate through the synced issue tracker. Multi-user support is on the roadmap.
A board for you, an API for your agents
One flat price for you and every agent you connect.
Start building