KaryaBoard's GitHub integration connects repositories to projects so engineering work on the board can stay tied to real commits. You authenticate with GitHub OAuth, choose repos for a project, and link commits to tasks as delivery progresses. The integration is available on Pro and Scale plans where the github feature flag is enabled — Free focuses on Kanban collaboration without repo connection.
What the integration does
The goal is simple: when someone ships code, the related task should show that commit context. OAuth gives KaryaBoard access to repository lists and the commit metadata needed to associate work. Once a project is linked, GitHub-aware workflows in the product can surface repos and commit linking next to tasks instead of forcing you to paste SHAs into comments by hand.
Privacy and scope matter. KaryaBoard uses GitHub as an optional integration, not as the login provider for the product. Sign-in remains through KaryaBoard accounts (for example email or Google via Firebase Authentication). Connecting GitHub grants repository-related access needed for listing repos and linking commits; disconnect when a client engagement ends or a repository should leave the workspace.
This page does not claim automated pull-request review bots, merge-queue orchestration, or CI replacement. KaryaBoard is a Kanban and planning product with GitHub commit linking — not a full DevOps platform. If your evaluation checklist requires automated PR review as a built-in feature, treat that as out of scope for the current integration and evaluate specialized tools separately.
How teams typically set it up
- Upgrade to Pro or Scale if GitHub is not available on your current plan. See pricing for member limits, trials, and annual totals.
- Open the project where engineering work lives and start the GitHub connect flow (OAuth).
- Authorize the requested repository access in GitHub.
- Select the repositories that belong to that project.
- As commits land, link them to the tasks they implement so the board reflects delivery, not only status column moves.
Agencies and multi-client studios often keep one KaryaBoard workspace with separate projects per client, then attach each client's repos to the matching project. That keeps commit context from leaking across unrelated boards. For workspace patterns aimed at client work, see KaryaBoard for agencies.
Boards, Stories, and agent workflows
GitHub linking is most useful when tasks are already structured. Pro and Scale also include Stories and AI-assisted generation: draft work from a story, review the proposed tasks, then execute against GitHub. Human approval before applying generated structure remains part of the product philosophy — the same review-before-commit idea used when Claude drafts a board through MCP.
Claude can operate the board through the hosted MCP server while GitHub remains the code host. Pair Claude at Settings → Claude MCP, enable specific boards, and let the agent create or update tasks while engineers link commits to those tasks. The MCP host is mcp.karyaboard.com with connector URL https://mcp.karyaboard.com/mcp. Overview and tool list: MCP for Claude. Procedural setup: MCP docs.
Together, the stack looks like this: Stories and tasks define intended work; the Kanban board shows status; GitHub commit links prove code moved; Claude (optional) helps with intake and hygiene through MCP tools. None of those layers invent fake velocity scores — they keep artifacts humans already use in one workspace.
When GitHub integration helps — and when it does not
It helps when your team already develops on GitHub and wants the board to show commit evidence next to tasks. It helps when multiple repos map cleanly to projects. It helps when you want AI and Stories on the same plan that unlocks GitHub.
It is a weaker fit if you need deep GitHub App automation, organization-wide policy engines, or native PR review workflows. KaryaBoard does not position itself as a replacement for GitHub Projects, CODEOWNERS enforcement, or enterprise audit products outside its own Scale plan flags (advanced permissions, audit log, invoice billing). Choose tools for what they actually ship.
Plans and documentation
Public catalog prices: Free at $0 (3 members, 3 projects) without GitHub; Pro at $49/month (25 members, Stories/AI/GitHub, 14-day trial, annual $468); Scale at $99/month (50 members, then $6 per extra member, trial length as returned by the live plans API — currently documented here as 30 days for Scale — annual $948, with advanced permissions, audit, and invoice billing flags). Confirm live numbers on pricing and in-app billing.
Step-by-step connect and linking notes live in the GitHub docs. For a broader product onboarding path, start at docs. Questions about account data copies or deletion requests go to support@karyaboard.com — there is no separate self-serve data-export product feature claimed on this marketing site.
KaryaBoard keeps the GitHub story narrow on purpose: OAuth connect, repos on projects, commits on tasks, GitHub-aware workflows for teams that ship software. Use it when that is the glue you need between Kanban and code — and pair it with MCP when Claude should help operate the same board.