Integrations
Last reviewed:
Kiantu assembles your work record from the tools you already use. Humans
connect with two clicks; agents connect with one MCP config line. Every
page below is also available in condensed machine-readable form at /llms.txt and /llms-full.txt.
Built for how you work
Dev teams
Commits, PRs, and tickets already describe your work — connect GitHub and Jira and sessions get corroborated by what actually shipped. Run the verbs from Slack or the terminal, and let your AI agents file their own hours over MCP — with per-agent budgets so a runaway loop can't surprise you.
Consultants, lawyers & client work
Client-billable days without a stopwatch culture: meetings land from Google or Outlook Calendar, quick session starts happen over WhatsApp between meetings, and reports reconcile the day into something you can put in front of a client.
Solopreneurs
Run the business from your phone: text WhatsApp to start "invoicing clients" from the road, keep tomorrow honest with the plate, and see where the week actually went — without adopting a heavyweight PM tool for a team of one.
AI agents & API
For people who live in a shell: session verbs as a 3 MB binary, no window, no Electron — and the same binary is the MCP server for your agents.
- kiantu start / stop / pause / resume / status from any shell
- kiantu mcp turns it into an MCP server for Claude Code & friends
- Scriptable: wire it into git hooks, tmux, or your deploy scripts
AI agents do real work now — MCP makes them first-class actors in Kiantu, with their sessions, cost, and output attributed and budgeted like any teammate.
- One config line connects Claude Code, Cursor, or any MCP client
- Agents report tokens + cost per model — spend shows up in reports
- report-only tokens: agents write their own record, read nothing else
Anything you can't click, you can script — the same REST API the app uses, with token auth and stable error codes.
- Log activity events from deploys, cron jobs, and test runs
- Start and close sessions from your own tools
- Machine-readable spec at /openapi.yaml
Chat platforms
Your team already lives in Slack — Kiantu meets them there, so tracking doesn't require opening another tab or breaking flow.
- Start, pause, and close sessions without leaving the conversation
- Assign work to a teammate's plate mid-thread — capacity-aware
- Nudges arrive as DMs, so forgotten timers get caught early
For teams and communities that run on Discord — the same session verbs, native slash commands, zero context switching.
- /kiantu slash commands with instant autocomplete
- Link once with a code, then every command is attributed to you
- Works per-server — install where your team actually talks
Enterprise teams shouldn't have to leave Teams to keep their work record honest — the Kiantu bot brings the verbs to them.
- Chat with the bot 1:1 — plain words, no syntax to learn
- Tenant-connect ceremony keeps IT in control of the install
- Same session model as the app, synced instantly
Between client meetings, on the road, or off the laptop entirely — a WhatsApp message keeps the record going. Built for people whose office is their phone.
- Text 'start invoicing clients' and the session is running
- Works on the number you already use — link once with a code
- Kiantu never messages you first; you text it, it answers
Issue trackers
Your tickets already describe the work — import them so sessions, reports, and agents can reference real issues instead of retyping them.
- Issues sync into Kiantu tasks with deep links back to Jira
- Projects map automatically; status categories translate cleanly
- OAuth once, then scheduled sync keeps it fresh
Code
Commits, PRs, and reviews are the ground truth of engineering work — connect them and your sessions get corroborated by what actually shipped.
- Pushes, PRs, reviews, and branch activity land in your timeline
- The correlation engine links code events to the session you ran
- Webhook-driven: near-real-time, no polling lag
Calendars
Meetings are work too — sync them and your day's record stops having mysterious gaps that reports can't explain.
- Events appear alongside sessions in the timeline
- Read-only scope: Kiantu sees busy time, never edits your calendar
- Meeting-heavy days finally reconcile with tracked time
Same as Google Calendar, for Microsoft shops — meetings flow into the work record so the day adds up.
- Events appear alongside sessions in the timeline
- Read-only Calendars.Read scope
- Works with the same Microsoft login you sign in with
For developers
The full API reference lives at /developers, with
the machine-readable spec at /openapi.yaml.