KaryaBoard

KaryaBoard MCP server for Claude

Connect Claude to KaryaBoard with the hosted MCP server at mcp.karyaboard.com — pairing, tools, and connector setup.

KaryaBoard exposes a hosted Model Context Protocol (MCP) server so Claude can read and update your boards through a controlled connector. The public host is https://mcp.karyaboard.com. The connector endpoint Claude uses is https://mcp.karyaboard.com/mcp. Pairing and board access are managed inside the product at app.karyaboard.com under Settings → Claude MCP. Claude's own connector UI lives at https://claude.ai/customize/connectors.

Why teams connect Claude to KaryaBoard

Software work rarely stays inside a chat window. Tasks live on a board, columns encode status, and comments capture decisions. Without a bridge, an assistant can only talk about work — it cannot list projects, create columns, open tasks, or mark items complete. The KaryaBoard MCP connector is that bridge: Claude calls named tools against your workspace, and those tools write through the same product APIs your team already uses in the browser.

Access is not all-or-nothing. After you pair, you choose which boards Claude may touch. Claude appears as a member on the boards you enable, so teammates can see agent-driven activity in the same place they review human updates. If a board should stay private to people only, leave it unchecked in Settings → Claude MCP.

Claude connector setup (copy-paste checklist)

  1. Sign in at https://app.karyaboard.com and open Settings → Claude MCP.
  2. Copy the MCP connector URL: https://mcp.karyaboard.com/mcp
  3. Open Claude connectors: https://claude.ai/customize/connectors
  4. Add a custom connector that points at https://mcp.karyaboard.com/mcp.
  5. In KaryaBoard Settings → Claude MCP, choose Generate pairing code. Codes expire after a short window — use a fresh code if pairing fails.
  6. Complete pairing in Claude with that code, then return to KaryaBoard and enable the boards Claude should access. Save board access before starting a new chat.
  7. Open a new Claude conversation, enable the KaryaBoard connector, and ask Claude to list_projects as a smoke test.

If status stays disconnected, regenerate the pairing code and try again. For stuck sessions, email support@karyaboard.com. You can disconnect MCP from the same Settings screen when you want to revoke the connector.

Tools available today

The hosted connector registers the following tools. Names are stable strings Claude discovers through MCP; arguments are validated on the connector before calls hit KaryaBoard APIs.

  • list_projects — list projects/boards the paired account can access
  • create_board — create a project/board with default or custom columns
  • update_board — rename, update description, or archive a board
  • get_board — fetch columns and tasks; optional includes for dependencies, activity, members, or placeholders
  • create_column — add a column to a board
  • create_task — create a task (dependencies, assignees, checklist, dates)
  • create_action_task — create an action task with CTA label/URL and optional reference fields
  • create_tasks_bulk — create up to 100 tasks in one column (all-or-nothing on validation failure)
  • update_task — partial task update, including move/complete helpers
  • mark_task_complete — mark complete or reopen; may require confirm bypass when blockers remain
  • comment_task — post a comment on a task
  • draft_board_from_document — propose a board structure from document text for human review
  • commit_drafted_board — create a board from an approved draft proposal

Draft-then-commit is intentional. draft_board_from_document proposes columns and tasks from text you provide; nothing lands on the workspace until you (or Claude, after your approval) call commit_drafted_board with the reviewed proposal. That pattern matches how KaryaBoard treats Stories and AI-assisted planning elsewhere in the product: generate, review, then apply.

Practical workflows

A common first workflow is intake. Paste a short project brief into Claude, ask it to draft a board, review the proposed columns and task titles, then commit. From there, Claude can create action tasks for external follow-ups, bulk-create implementation tickets into a Ready column, and comment when it finishes a step. Engineers still move work across the Kanban board in the UI; the agent fills gaps that would otherwise sit in chat history.

Another workflow is status hygiene. Ask Claude to get_board, summarize blocked items, and comment on tasks that need a decision. Because comments and task updates appear in KaryaBoard, the board remains the source of truth — Claude is a client, not a parallel tracker.

Teams that also use GitHub can keep delivery context on the same board. MCP does not replace the GitHub integration; it complements it. Connect repos and link commits through the product's GitHub features on Pro or Scale, then let Claude operate tasks while commits attach to the work items those tasks represent. See GitHub integration for how OAuth and commit linking work.

Plans, limits, and related docs

MCP pairing is part of the KaryaBoard product surface; board creation and collaboration still follow your plan's member and project limits. Free is suitable for trying the board with a small group. Pro and Scale unlock Stories, AI-assisted generation, and GitHub features that often sit next to agent workflows. Full public prices and trial lengths are on the pricing page.

For step-by-step connector notes, board access controls, and troubleshooting, read the MCP documentation. If you are new to the product, start with getting started, then return here once you have at least one project to enable for Claude.

KaryaBoard is built for coding agents and small-to-medium software teams that want Kanban without enterprise process overhead. The MCP server is the open interface for Claude to participate in that board — with pairing you control, tools you can name in prompts, and writes that show up where your team already looks.