KirinBoard
OnlineNewRead-only agent claims, CI status and delivery data from a KirinBoard workspace
What it can do: 18 tools
boardread-onlyCall this before you claim or start an issue. One call returns, for the repository you are working in: every active claim (issue, phase, who, tool and model, branch, PR and checks, last active, live or stale); your own clist_projectsread-onlyThe repositories (projects) this token can read, by owner/name.ci_statusread-onlyPushes queued, running or finished in the last hour, with their outcome and checks; with a branch, that branch only (looking back 12 hours if it has nothing in the last hour). For pushes that finished more than an hour awho_holdsread-onlyWhether anyone holds issue #N now (live or stale claim), and who last worked on it (the agent stamped on its pull request).live_sessionsread-onlyAgent sessions on a repository and the issues each holds: who, tool and model, state, last active. Live sessions only unless include_stale.delivery_summaryread-onlyWhat was opened, worked on and closed in a window: counts by phase, blocked items, and the most recently closed. Give days (1 to 90, default 14) or from and to (YYYY-MM-DD).almost_doneread-onlyFinds the last tickets that would finish an initiative, and which of them are free to pick up. An initiative is a parent ticket that groups the tickets of one larger piece of work. For a repository it lists the initiativgate_complianceread-onlyShows how a repository's pull request gates have fared over the last 7 and 30 days. A gate is a check the dashboard grades every pull request by (for example agent identity, persona, or "closes an issue"). For each gate:ci_historyread-onlyAnswers "did the push I made a few hours ago pass?". Lists the pushes on a repository that finished between 1 and 12 hours ago (or 1 and 4 hours ago), newest first, each with its branch, pull request, title, who pushed iquick_winsread-onlyLists what is closest to finished in a repository, so you can pick work that completes something. Two lists, in the dashboard's Quick wins order: initiatives (an initiative is a parent ticket that groups the tickets of ooperationsread-onlyCall this before you start a shared operation such as a deploy or a restart (deploy:production, restart:api), to see whether another agent is already doing it. For a repository it lists the operations an agent holds, orneeds_youread-onlyLists what needs a person on a repository, as the dashboard's Needs you panel does and in its order, most urgent first: the main branch failing CI, failing pull requests nobody is on, work held by a session that has endeci_queueread-onlyCall this before you push, to judge whether your job will wait for a runner and whether now is a busy time. For a repository it shows: what is waiting for a runner now (jobs, grouped by pull request or push, and the runnmetrics_historyread-onlyThe dashboard's daily metric history for a repository, oldest day first, for trends: is CI getting slower or failing more, is the backlog growing, are runners congested more often? Each day carries what the dashboard recsettingsread-onlyThe thresholds the dashboard uses to judge a repository, as its team set them, and where each value comes from (the repository, the workspace, a settings file, or the default): when an in-progress item counts as stalled,left_behindread-onlyAnswers "what did I or another session start and leave?". For a repository it lists three things. Left behind: open work held by a session that has ended, one row per open pull request (else per issue), most recently actsub_issue_limitread-onlyLists the initiatives in a repository, and the container issues inside them, that hold at least the dashboard's threshold (default 70) of the 100 sub-issues GitHub allows one parent, fullest first: each with its sub-issuarea_suggestionsread-onlyLists the open issues in a repository that have no area (no [persona] title prefix and no persona: label), as the dashboard's Has an area line counts them, each with a suggested area, the persona: label that gives it, a
Connect it
claude mcp add --transport http kirinboard https://app.kirinboard.ai/mcpSettings → Connectors → Add custom connector
URL: https://app.kirinboard.ai/mcp{
"mcpServers": {
"kirinboard": {
"url": "https://app.kirinboard.ai/mcp"
}
}
}{
"servers": {
"kirinboard": {
"type": "http",
"url": "https://app.kirinboard.ai/mcp"
}
}
}Questions
What does KirinBoard do?
Read-only agent claims, CI status and delivery data from a KirinBoard workspace It exposes 18 tools to AI assistants.
What tools does KirinBoard provide?
18 tools, including board, list_projects, ci_status, who_holds, live_sessions, delivery_summary, almost_done, gate_compliance, ci_history, quick_wins, operations, needs_you….
How do I connect KirinBoard to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://app.kirinboard.ai/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does KirinBoard require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is KirinBoard online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes KirinBoard?
kirinboard.ai. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Project Management
-
SanityOnline · sign-in requiredPopular
Gives AI agents direct access to your Sanity projects and guidance for working with them
-
LinearOnline · sign-in requiredOfficialPopular
Find and manage issues, projects, and documents in your Linear workspace.
-
ReqResOnlineOfficial
Hosted backend for AI agents: create projects with persistent collections and keys, no signup.
-
ChainstackOnlineOfficial
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
-
Singularity AppOnline · sign-in requiredOfficialNew
Manage tasks, projects, habits, Kanban boards, and time tracking with SingularityApp.
-
Release AlertOnlineOfficialNew
Connect AI assistants to Release Alert.