How do I use Flow Boards MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Flow Boards MCP Server Create a user story in the Backlog flow" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Flow Boards MCP Server

by Germanicus1

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

@mauvable/flowboards-mcp

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>"
      }
    }
  }
}

Related MCP server: VoIPbin MCP Server

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.

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

Available Tools

38 tools

add_commentB

Add a comment to a ticket.

Inputs: comment (required), ticketId (required), format.

archive_ticketsB

Archive one or more tickets.

Inputs: ids (required).

create_binC

Create a new bin.

Inputs: name (required), flowId (required).

create_ticketA

Create a new ticket in a flow. Accepts flow name and ticket type name — resolves IDs automatically.

Inputs: flow (required), name (required), ticketType (required), bin, +1 more.

create_webhookC

Create a new webhook.

Inputs: url (required), events.

delete_commentA

Delete a comment by ID.

Inputs: id (required).

delete_ticketC

Delete a ticket by ID.

Inputs: id (required).

delete_ticketsA

Delete multiple tickets by ID.

Inputs: ids (required).

delete_webhookA

Delete a webhook by ID.

Inputs: id (required).

get_binA

Get details for a specific bin by name or ID.

Inputs: bin (required).

get_boardA

Get details for a specific board by name or ID.

Inputs: board (required).

get_commentA

Get a specific comment by ID.

Inputs: id (required).

get_flowB

Get details for a specific flow by name or ID.

Inputs: flow (required).

get_ticketA

Get details for a specific ticket by ID.

Inputs: id (required).

get_userA

Get a user by ID or email.

Inputs: idOrEmail (required).

invite_userA

Send an invitation to a new user.

Inputs: email (required).

link_to_parentA

Link one or more tickets to a parent (epic). Stories become children of the epic.

Inputs: ids (required), parentId (required).

list_binsB

List all bins.

Inputs: no named parameters.

list_boardsA

List all boards.

Inputs: no named parameters.

list_commentsA

List all comments for a ticket.

Inputs: ticketId (required).

list_custom_fieldsB

List all custom fields.

Inputs: no named parameters.

list_flow_movesB

List ticket movement history within a flow.

Inputs: flow (required).

list_flowsA

List all flows with their bins and metadata.

Inputs: no named parameters.

list_flow_ticketsB

List all tickets in a flow.

Inputs: flow (required).

list_ticket_movesB

Get the movement history for a ticket.

Inputs: id (required).

list_ticketsB

List tickets filtered by bin, parent, or child.

Inputs: binId, childId, parentId.

list_ticket_typesA

List all ticket types (e.g. User Story, Epic, Bug).

Inputs: no named parameters.

list_user_groupsA

List all user groups.

Inputs: no named parameters.

list_usersA

List all users in the organisation.

Inputs: no named parameters.

list_webhooksA

List all webhooks.

Inputs: no named parameters.

move_ticketA

Move a ticket to a different bin (workflow stage).

Inputs: id (required), bin (required).

restore_ticketsA

Restore one or more archived tickets.

Inputs: ids (required).

search_ticketsC

Search tickets by text or criteria.

Inputs: query (required).

test_webhookA

Send a test payload to a webhook.

Inputs: id (required).

unlink_from_parentA

Remove parent relationship from one or more tickets.

Inputs: ids (required).

update_binA

Update a bin's name or configuration.

Inputs: bin (required), name.

update_commentC

Update a comment's text.

Inputs: id (required), comment (required), format.

update_ticketC

Update ticket fields (name, description, bin, etc.).

Inputs: id (required), name, binName, description.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

B3.4/5.0

Scored 2026-08-02 12:55 across 38 tools

Disambiguation4/5

Most tools are clearly scoped to distinct resources (tickets, flows, bins, boards, comments, users, webhooks). However, update_ticket and move_ticket have overlapping functionality since update_ticket can also change the bin field, which may cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, update_, delete_, etc.). Minor deviations like link_to_parent and unlink_from_parent still follow a predictable structure.

Tool Count2/5

With 38 tools, this server is over-scoped for typical MCP usage. While it covers many resources, the high number of simple list/get operations (e.g., list_flows, list_bins, list_boards, list_ticket_types) could be consolidated.

Completeness4/5

The tool surface covers the core ticket lifecycle (create, get, update, move, delete, archive, restore) and supports comments, linking, and webhooks. Missing functionality includes board management (no create/update/delete) and bin deletion, but these are minor gaps.

Maintenance

ActivityInactive

ResponsivenessOutdated data

Resources

Related MCP Connectors

Flowra
io.github.flowradev
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Agent Orchestration Autonomous Agents
11
https://mcp.flowra.dev/mcp
mcp-server
com.niftypm
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Project Management Communication File Systems
2
https://mcp.niftypm.com/mcp
jumpcloud-genai
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2
https://mcp.jumpcloud.com/v1
secureflows-mcpA
io.github.michal-lefler
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Code Analysis Developer Tools Security
181
https://www.secure-flows.com/mcp

Related MCP Servers

paperclip-mcp
Agent Orchestration Project Management
bruhsb
A
license
A
quality
D
maintenance
MCP server that exposes the Paperclip control plane API as tools for Claude Code agents — manage issues, coordinate agents, post comments, and orchestrate work without direct API calls.
Updated 6 months ago (2026-04-28 19:32 UTC)
100
34 npm
2
MIT
VoIPbin MCP Serverofficial
Communication Email
voipbin
A
license
B
quality
B
maintenance
An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
Updated a month ago (2026-10-10 04:11 UTC)
66
1
MIT
Langflow MCP Server
AI & Machine Learning RAG Systems Agent Orchestration
mdnazisharman
A
license
Not graded
quality
D
maintenance
MCP Server for interacting with the Langflow API via a natural language interface. It exposes Langflow functionalities as tools for LLMs.
Updated a year ago (2025-06-24 04:57 UTC)
MIT
miro-remote-mcp
Design Tools Workplace & Productivity
FlyAgileWithGiom
F
license
Not graded
quality
D
maintenance
An MCP server that enables Claude AI to programmatically create and manipulate Miro boards via the Miro API with OAuth2 authentication. Supports 14 tools for board, item, and connector operations.
Updated 8 months ago (2026-03-05 11:33 UTC)
-

@mauvable/flowboards-mcp

Installation

Configuration

Available Tools

Tickets

Flows

Bins

Boards

Comments

Other

Example Usage

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

paperclip-mcp

VoIPbin MCP Serverofficial

Langflow MCP Server

miro-remote-mcp