KirinBoard
Read-only agent claims, CI status and delivery data from a KirinBoard workspace
What it does
KirinBoard is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)Hosted endpoint
https://app.kirinboard.ai/mcpstreamable-http
In Claude Code: claude mcp add --transport http kirinboard https://app.kirinboard.ai/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"kirinboard": {
"url": "https://app.kirinboard.ai/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1h agoONLINE KirinBoard answered an MCP connection on 04 Nov 2026 and introduced itself as kirin-devops 0.1.1 (MCP protocol 2025-06-18).
18 tools offered to AI assistants
board· Call 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 claims, if you pass slist_projects· The repositories (projects) this token can read, by owner/name.ci_status· Pushes 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 ago, use ci_history.who_holds· Whether anyone holds issue #N now (live or stale claim), and who last worked on it (the agent stamped on its pull request).live_sessions· Agent sessions on a repository and the issues each holds: who, tool and model, state, last active. Live sessions only unless include_stale.delivery_summary· What 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_done· Finds 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 initiatives the dashboard clagate_compliance· Shows 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: how many pull requeci_history· Answers "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 it, outcome (passed,quick_wins· Lists 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 one larger piece of woperations· Call 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, or held in the last 24needs_you· Lists 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 ended, green or approved
Show 6 more
ci_queue· Call 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 runner labels they waitmetrics_history· The 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 recorded that day: issusettings· The 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, how few tickets lefleft_behind· Answers "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 active first: the issuesub_issue_limit· Lists 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-issue count, how many ofarea_suggestions· Lists 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 confidence (high or
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 0.1.1 | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| Hosted endpoint | https://app.kirinboard.ai/mcp | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| Website | https://kirinboard.ai | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 2d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 2d ago |
Change history
- VERSION02 Nov 20260.1.0 → 0.1.1
- NEW01 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is KirinBoard still online?
Free alerts · no account▲ 0Do you run KirinBoard? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Are you the publisher of KirinBoard?
Free · show your listingAn independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.
<a href="https://electraindex.com/mcp/kirinboard?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/kirinboard" alt="Listed on Electra Index"></a>Questions about KirinBoard
How do I connect KirinBoard?
Use the hosted endpoint https://app.kirinboard.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does KirinBoard offer?
When Electra Index connected on 04 Nov 2026, it listed 18 tools: board, list_projects, ci_status, who_holds, live_sessions, delivery_summary, almost_done, gate_compliance and more. The full list is in "Live check" above.
Is KirinBoard online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.