Use case: software teams
Releases, bugs and docs your coding agent can read.
Plan work on Kanban boards, write specs and runbooks in the wiki, and connect Claude Code, Codex or Cursor through MCP. A REST API and webhooks connect the rest of your tools.
- Product and engineering teams
- Open-source maintainers
- Developers who work with agents
The problemBugs, features and release tasks are spread over issues, chats and spreadsheets.
One board for the release, four ways to see it.
Start from the Software development template. See the same tasks as a board, in swimlanes by priority, on a calendar or in a sortable table.
- Task keys such as APP-123 to name work in reviews and chats.
- Priorities from low to urgent, due dates, labels and checklists.
- A soft WIP limit per list warns when work piles up.
- Done tasks in the done list are never overdue.
The problemYour coding agent can read the code, but not the plan.
Connect your coding agent with MCP.
Claude Code, Codex and Cursor can read tasks, comment, move work and update wiki pages through the Kanroo MCP server. The agent uses your personal API key, so it can do only what you may do.
- 116 MCP tools (October 2026), for boards, tasks and the wiki.
- Read, Write or Admin scope per key.
- A remote endpoint, or a local server for work with files.
- No built-in AI: you choose the agent.
The problemYour pipeline and chat tools need to know when work changes.
A REST API and webhooks for the rest.
The REST API is contract-first and described in an OpenAPI 3.1 file. Webhooks tell your systems when tasks, lists, comments, checklists or wiki pages change.
- Personal API keys with a scope and an optional expiry date.
- Webhooks signed with the Standard Webhooks headers.
- Retries and a delivery log for every webhook.
- Import from CSV or Trello JSON. Export boards as JSON or CSV.
Webhooks are on every Kanroo Cloud plan. A self-hosted server needs the Enterprise Edition for them.
Webhooks documentationThe problemSpecs and runbooks drift away from the work.
Docs next to the tasks.
Write specs, runbooks and release notes in the wiki. Link pages from tasks and tasks from pages, so the context is one click away.
- Markdown with code, tables and Mermaid diagrams.
- Version history for every page.
- Import a folder of Markdown files. Export a space as a ZIP.
- Search with ShiftK covers tasks, boards and pages.
Features you will use
Every one of them is on every Kanroo Cloud plan.
Questions and answers
Does Kanroo connect to GitHub or GitLab?
Not directly yet. Use webhooks and the REST API to connect your pipeline, or let your coding agent update tasks through MCP. A native integration may come with community interest, so request it through the feedback form.
Request a featureCan we import from Jira?
There is no native Jira import. Export your issues as CSV and map the columns in the CSV import. Every import shows a preview first, so nothing changes until you confirm.
Does Kanroo have sprints, story points or subtasks?
Not as built-in features. Many teams use one board or one list per release, and labels for size. Custom fields and subtasks are not built yet.
Is the MCP server part of the open-source core?
Yes. Both the remote endpoint and the local server are part of the open-source core.
Other use cases
- Service deskPublic forms and email create tasks. Labels sort them, a public board shows the status, and the wiki answers common questions.
- AgenciesOne board per client project, one wiki space per client, and read-only links that keep each client in the loop.
- Public sectorWorkspace data in the EU, an open-source core you can self-host, keyboard and screen-reader design, and no built-in AI.
Set it up on your own board.
Every feature is on every Kanroo Cloud plan. Try it alone for free, then invite your team.