KirinBoard

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://app.kirinboard.ai/mcp

claude mcp add --transport http kirinboard https://app.kirinboard.ai/mcp

{
  "mcpServers": {
    "kirinboard": {
      "url": "https://app.kirinboard.ai/mcp"
    }
  }
}

{
  "servers": {
    "kirinboard": {
      "type": "http",
      "url": "https://app.kirinboard.ai/mcp"
    }
  }
}

https://app.kirinboard.ai/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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 session_id or branch; unclaimed issues in

• list_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 classes as almost done (a few tickets left

• gate_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 requests passed it, failed it, would have fai

• ci_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, failed, awaiting, superseded), when it f

• 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 work) with open tickets, almost done firs

• operations

  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 24 hours: the operation, who holds it, sinc

• needs_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 pull requests left unmerged, pull reque

• 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 wait on), how long the oldest has waited and

• metrics_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: issues filed and closed and open, CI runs pa

• settings

  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 left and how much closed make an initiative

• left_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 issue or pull request with its title and link

• sub_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 of those are closed, how many slots are fr

• area_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 medium) and a one-line reason. The sugge

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (kirinboard.ai) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 426 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 18 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32568 servers in this category
• Published to the registry more recently than 87% of the other 32568 servers in this category
• Basic checks equal to or better than 37% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo