Flow Boards Server

MCP server for Flow Boards — exposes the full Flow Boards REST API as Claude tools.

Installation

Add to your Claude / MCP-compatible AI tool config:

{
  "mcpServers": {
    "flowboards": {
      "command": "npx",
      "args": ["-y", "@mauvable/flowboards-mcp"],
      "env": {
        "FLOW_BOARDS_URL": "https://<host>/rest/2/<org-id>",
        "FLOW_BOARDS_TOKEN": "<your-bearer-token>"
      }
    }
  }
}

Configuration

Variable	Description
FLOW_BOARDS_URL	Full API base URL including org path, e.g. https://n1.fb.mauvable.com/rest/2/<org-id>
FLOW_BOARDS_TOKEN	Bearer token for authentication

Available Tools

Tickets

• create_ticket — Create a ticket in a flow (accepts flow name, resolves IDs automatically)
• get_ticket — Get ticket details
• list_tickets — List tickets by bin, parent, or child
• update_ticket — Update ticket fields
• move_ticket — Move ticket to a different bin
• delete_ticket / delete_tickets — Delete one or many tickets
• archive_tickets / restore_tickets — Archive or restore tickets
• link_to_parent — Link stories to an epic
• unlink_from_parent — Remove parent relationship
• list_ticket_moves — Movement history for a ticket

Flows

• list_flows — List all flows
• get_flow — Get flow details
• list_flow_tickets — List tickets in a flow
• list_flow_moves — Movement history for a flow

Bins

• list_bins / get_bin — List or get bins
• create_bin / update_bin — Create or update bins

Boards

• list_boards / get_board

Comments

• add_comment — Add a comment to a ticket
• list_comments / get_comment — Read comments
• update_comment / delete_comment

Other

• list_ticket_types — Available ticket types (User Story, Epic, etc.)
• list_custom_fields
• list_users / get_user / invite_user
• list_user_groups
• search_tickets
• list_webhooks / create_webhook / delete_webhook / test_webhook

Example Usage

Once configured, just talk to Claude naturally:

"Create 3 user stories in the Backlog flow" "Move all stories in 'In Progress' to 'Done' in the Dev flow" "Add a comment 'Ready for review' to ticket abc123" "Link stories X, Y, Z to epic E"

...or if you like a fully automated flow you can give Clause the instructions to move tickets when it has done it's job.

1. Create User Stories and Epics from the attached reqirements documetent and put them into the backlog.
2. Link the apropiate User Stories as child tickets to their Epics.
3. Create an implementation plan.
4. Execute the implementation plan.
5. Move the User Stories and their Epic from the next phase in teh implementation plan, into the Next bin.
6. When you you start developing the first user story move it into the Developing bin. Move its parent Epic into Developing too.
7. When a user Story is done, move it into the Done bin and commit it to git.
8. Epics move automatically to the Done bin when all their child tickets are done.
9. After each phase ask me if I wan tto continue.