Board, sprints, time tracking, GitHub sync — and MCP tools that let Claude Code, Cursor, and Codex manage your issues without you ever opening a browser.
Currently in active development.
Every feature. Every tier. No add-on pricing.
Log time per issue, filter by project or date range. Export-ready data for invoicing. No Toggl subscription needed.
MCP tools let Claude Code, Cursor, and Codex read issues, log time, move cards, and plan sprints — all from your terminal. No browser needed.
Amsterdam-hosted, database-per-tenant isolation. Your data physically stays in the EU. Built for GDPR from day one, not retrofitted.
One tool. No switching. No noise. Built for developers who ship, not developers who administrate.
Scope the sprint. Assign the work. Unfinished issues carry over automatically when the sprint closes.
One click per issue. Filter by project or date range. Export to XLSX when the invoice is due.
Branch linked. PR synced. Code merged — card moves to Done. Webhook-driven, zero manual updates.
Group issues into epics. Set start and end dates. Track progress across sprints. Your roadmap, not a spreadsheet.
Hash-chained logs. Tamper-proof by design. Every action recorded — including AI calls.
Five roles from Admin to Viewer. Two-tier authorization — permissions enforced at both the gate and the action. No shortcuts.
When your agent is coding, it should know the full picture — and keep it current.
$ kendo issue create --title "Add SAML SSO" \ --priority high --sprint "Sprint 12" ✓ Created KEN-84: Add SAML SSO Priority: High · Sprint: Sprint 12 · Assigned: you $ kendo board Sprint 12 — Acme Platform +----------+----------+----------+----------+ | To Do 4 | Doing 2 | Review 1 | Done 11 | +----------+----------+----------+----------+ | KEN-84 * | KEN-71 | KEN-68 | KEN-52 | | KEN-79 | KEN-75 | | KEN-49 | | KEN-77 | | | ...+9 | | KEN-76 | | | | +----------+----------+----------+----------+ $ kendo time log 2h --issue KEN-84 ✓ Logged 2h on KEN-84: Add SAML SSO Today: 4h 30m · Sprint total: 31h 15m
kendo ships a Go-based command-line interface so you can hit your board from any terminal window — create issues, check the board, log time — without switching context to a browser. Think gh for project management.
Use MCP when your AI assistant is working. Use the CLI when you are. Both talk to the same board.
Install the CLISide by side. No marketing fluff — just what ships.
| Feature | kendo.dev | Linear | Jira | GitHub Projects | Plane |
|---|---|---|---|---|---|
| Kanban board | ✓ | ✓ | ✓ | ✓ | ✓ |
| Sprint planning | ✓ | ✓ (Cycles) | ✓ | ✗ | ✓ (Cycles) |
| Built-in time tracking | ✓ All tiers | ✗ | Add-on | ✗ | Pro+ |
| MCP server | ✓ | ✓ | ✗ | ✗ | ✓ |
| CLI tool | ✓ | ✗ | ✗ | ✗ | ✗ |
| GitHub sync | ✓ | ✓ | Marketplace | ✓ Native | ✓ |
| Audit logging | ✓ Hash-chained | ✗ | Enterprise | Enterprise | Enterprise |
| EU data residency | ✓ Amsterdam | US | Enterprise | US | Self-host |
Board, sprints, time tracking, GitHub sync, and an MCP server for AI assistants. Built for dev teams. Hosted in Amsterdam. Currently in active development.
Tools and resources connect directly to Claude Code, Cursor, and Codex. Your AI reads issues, logs time, moves cards, and plans sprints — without leaving the terminal.
Time tracking is built in, not an add-on. Audit logs are hash-chained, not an enterprise upsell. Data stays in Amsterdam, not Virginia. And the MCP server means your AI assistant is a first-class citizen.
Amsterdam. Each workspace gets its own database — physically separated from other tenants. GDPR-compliant by architecture, not by policy.
Join the waitlist and be the first to know when kendo.dev is ready.
By joining, you agree to our Privacy Policy .
In active development. Last deployed: 2026-04-07