Flow Boards MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_BOARDS_URL | Yes | Full API base URL including org path, e.g. https://n1.fb.mauvable.com/rest/2/<org-id> | |
| FLOW_BOARDS_TOKEN | Yes | Bearer token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_ticketA | Create a new ticket in a flow. Accepts flow name and ticket type name — resolves IDs automatically. |
| get_ticketA | Get details for a specific ticket by ID. |
| list_ticketsB | List tickets filtered by bin, parent, or child. |
| update_ticketC | Update ticket fields (name, description, bin, etc.). |
| move_ticketA | Move a ticket to a different bin (workflow stage). |
| delete_ticketC | Delete a ticket by ID. |
| delete_ticketsA | Delete multiple tickets by ID. |
| archive_ticketsB | Archive one or more tickets. |
| restore_ticketsA | Restore one or more archived tickets. |
| link_to_parentA | Link one or more tickets to a parent (epic). Stories become children of the epic. |
| unlink_from_parentA | Remove parent relationship from one or more tickets. |
| list_ticket_movesB | Get the movement history for a ticket. |
| list_flowsA | List all flows with their bins and metadata. |
| get_flowB | Get details for a specific flow by name or ID. |
| list_flow_ticketsB | List all tickets in a flow. |
| list_flow_movesB | List ticket movement history within a flow. |
| list_binsB | List all bins. |
| get_binA | Get details for a specific bin by name or ID. |
| create_binC | Create a new bin. |
| update_binA | Update a bin's name or configuration. |
| list_boardsA | List all boards. |
| get_boardA | Get details for a specific board by name or ID. |
| add_commentB | Add a comment to a ticket. |
| list_commentsA | List all comments for a ticket. |
| get_commentA | Get a specific comment by ID. |
| update_commentC | Update a comment's text. |
| delete_commentA | Delete a comment by ID. |
| list_ticket_typesA | List all ticket types (e.g. User Story, Epic, Bug). |
| list_custom_fieldsB | List all custom fields. |
| list_usersA | List all users in the organisation. |
| get_userA | Get a user by ID or email. |
| invite_userA | Send an invitation to a new user. |
| list_user_groupsA | List all user groups. |
| search_ticketsC | Search tickets by text or criteria. |
| list_webhooksA | List all webhooks. |
| create_webhookC | Create a new webhook. |
| delete_webhookA | Delete a webhook by ID. |
| test_webhookA | Send a test payload to a webhook. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
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.
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.
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.
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.