NestDaddy

KirinBoard

ai.kirinboard/kirinboard · v0.1.1

Read-only agent claims, CI status and delivery data from a KirinBoard workspace

Connect Remote server

Terminal
claude mcp add --transport http kirinboard https://app.kirinboard.ai/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "kirinboard": {
      "url": "https://app.kirinboard.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "kirinboard": {
      "type": "http",
      "url": "https://app.kirinboard.ai/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://app.kirinboard.ai/mcp

Tools 18 found in our last check

  • 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 i…

  • 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 fa…

  • 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…

  • 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 fir…

  • 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, sin…

  • 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 requ…

  • 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 p…

  • 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 initiativ…

  • 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 lin…

  • 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 f…

  • 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 sugg…

Details

Endpointhttps://app.kirinboard.ai/mcp (Streamable HTTP)
First published2 Nov 2026
Last updated2 Nov 2026
Registry nameai.kirinboard/kirinboard

More ai and media servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.