Agencies juggle multiple client workstreams at once: separate backlogs, different GitHub organizations, and contractors who should only see the boards they are staffed on. KaryaBoard supports that shape with multi-project boards in one workspace, plan-based member limits, MCP board access controls for Claude, and GitHub connections per project on Pro/Scale. This page describes those product capabilities — it does not invent agency case studies, win rates, or unnamed client logos.
One workspace, many client boards
In KaryaBoard, projects are the board containers you use day to day. An agency can keep a single workspace and create a project per client (or per client workstream). That keeps columns, tasks, comments, and Stories scoped to the engagement instead of mixing every retainer into one overloaded board. Free plans include up to 3 projects, which is enough to pilot the model; Pro and Scale remove the Free project cap so catalogs of clients can grow with the workspace.
Member limits are also plan-based: Free supports 3 members; Pro supports 25; Scale supports 50 with $6 per additional member. Agencies often combine full-time staff and rotating contractors — count seats against the plan before inviting everyone to every board. Role semantics in-product (such as owner, member, viewer) help constrain who edits versus who observes; Scale adds advanced permissions and audit-oriented flags for teams that need tighter admin controls.
MCP board access controls
Claude can connect through the hosted MCP server at https://mcp.karyaboard.com using connector URL https://mcp.karyaboard.com/mcp. Pairing happens in app.karyaboard.com under Settings → Claude MCP. After pairing, you choose which boards Claude may access. That checkbox list is the agency control plane: enable the active client board for agent-assisted intake, leave unrelated retainers disabled.
Useful MCP tools for agency workflows include list_projects, draft_board_from_document / commit_drafted_board for turning a statement of work into a proposed board, create_tasks_bulk for sprint-shaped task sets, create_action_task for client-facing CTAs, and comment_task for leaving visible notes. Full tool list and Claude connector steps: MCP and MCP docs.
Because Claude appears as a member on enabled boards, your team can audit agent activity next to human comments. When an engagement ends, disable the board for Claude and disconnect or rotate pairing as needed. Do not treat MCP as a second, invisible backlog — the board remains authoritative.
GitHub per project
Client code rarely lives in one mega-repo you share across accounts. KaryaBoard's GitHub integration (Pro/Scale, github feature flag) uses OAuth to connect repositories and supports GitHub-aware workflows with commit linking to tasks. Attach each client's repos to the matching project so commit context stays local to that board. Details and non-claims (no invented auto-PR review) are on GitHub integration and GitHub docs.
When a contractor finishes, remove their seat and review which repos remain connected. Workspace hygiene matters more in agencies than in single-product startups because access boundaries are contractual, not just cultural.
Stories and approval-friendly planning
Discovery docs and SOWs often arrive as prose. On plans with Stories and AI enabled, teams can generate task structure and review it before applying — the same approval instinct as MCP draft/commit. That reduces the risk of an assistant inventing a backlog the account lead never accepted. Pair human review with clear column conventions (for example Discovery, Ready, In progress, Waiting on client, Done) so status is understandable to both engineers and producers.
Pricing shape for agency planning
Public prices: Free $0 (3 members, 3 projects); Pro $49/month (25 members, Stories/AI/GitHub, 14-day trial, annual $468); Scale $99/month (50 members, $6 per extra member, annual $948, advanced permissions/audit/invoice flags; Scale trial duration follows the live public plans API — documented on the pricing page as 30 days for Scale). Start at https://app.karyaboard.com/signup. Full breakdown: pricing.
For account data copy or deletion requests related to a closed client workspace, email support@karyaboard.com. This site does not claim a self-serve data-export product feature.
A practical pilot without theater
A clean agency pilot looks like this: create one internal project and one client project on Free or a Pro trial; invite only the staffed humans; connect the client GitHub repos to the client project alone; pair Claude and enable solely that client board; draft a board from the SOW with draft_board_from_document, review with the account lead, then commit_drafted_board. After two weeks, decide whether the board became the place status questions get answered. If it did not, KaryaBoard is not yet your operating system — and that is a valid outcome.
Avoid dual-writing the same client work into three tools. If your company still requires Jira or Linear for internal reporting, keep KaryaBoard as the client delivery board and accept the export/summary cost at the boundary — or do not adopt a second board at all. Comparisons that state when other tools win: vs Jira, vs Linear, vs Trello.
What this page does not claim
No fabricated agency case studies, retention percentages, or “trusted by” client lists appear here. If you need references, ask support or evaluate with a real pilot board. KaryaBoard is operated by VioletStack Pvt Ltd — read Terms and Privacy for how the service is described legally.
Next steps: getting started, configure MCP for the boards you choose, connect GitHub where code delivery matters, and keep each client project as its own source of truth.