MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Flowboards is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for the FlowBoards workflow management API
Quickstart
# 1 — run it from where its publisher ships it
npx -y @mauvable/flowboards-mcp
# 2 — ask your agent something
> MCP server for the FlowBoards workflow management API
Flowboards is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
MAAll 1 server
@mauvable1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Flowboards as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add flowboards-mcp -- npx -y @mauvable/flowboards-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
38 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all bins.
Takes no parameters.
Example callreturns →
Get details for a specific bin by name or ID.
Takes no parameters.
Example callreturns →
Create a new bin.
Takes no parameters.
Example callreturns →
Update a bin\
Takes no parameters.
Example callreturns →
List all boards.
Takes no parameters.
Example callreturns →
Get details for a specific board by name or ID.
Takes no parameters.
Example callreturns →
Add a comment to a ticket.
Takes no parameters.
Example callreturns →
List all comments for a ticket.
Takes no parameters.
Example callreturns →
Get a specific comment by ID.
Takes no parameters.
Example callreturns →
Update a comment\
Takes no parameters.
Example callreturns →
Delete a comment by ID.
Takes no parameters.
Example callreturns →
List all flows with their bins and metadata.
Takes no parameters.
Example callreturns →
Get details for a specific flow by name or ID.
Takes no parameters.
Example callreturns →
List all tickets in a flow.
Takes no parameters.
Example callreturns →
List ticket movement history within a flow.
Takes no parameters.
Example callreturns →
List all ticket types (e.g. User Story, Epic, Bug).
Takes no parameters.
Example callreturns →
List all custom fields.
Takes no parameters.
Example callreturns →
List all users in the organisation.
Takes no parameters.
Example callreturns →
Get a user by ID or email.
Takes no parameters.
Example callreturns →
Send an invitation to a new user.
Takes no parameters.
Example callreturns →
List all user groups.
Takes no parameters.
Example callreturns →
Search tickets by text or criteria.
Takes no parameters.
Example callreturns →
List all webhooks.
Takes no parameters.
Example callreturns →
Create a new webhook.
Takes no parameters.
Example callreturns →
Delete a webhook by ID.
Takes no parameters.
Example callreturns →
Send a test payload to a webhook.
Takes no parameters.
Example callreturns →
Create a new ticket in a flow. Accepts flow name and ticket type name — resolves IDs automatically.
Takes no parameters.
Example callreturns →
Get details for a specific ticket by ID.
Takes no parameters.
Example callreturns →
List tickets filtered by bin, parent, or child.
Takes no parameters.
Example callreturns →
Update ticket fields (name, description, bin, etc.).
Takes no parameters.
Example callreturns →
Move a ticket to a different bin (workflow stage).
Takes no parameters.
Example callreturns →
Delete a ticket by ID.
Takes no parameters.
Example callreturns →
Delete multiple tickets by ID.
Takes no parameters.
Example callreturns →
Archive one or more tickets.
Takes no parameters.
Example callreturns →
Restore one or more archived tickets.
Takes no parameters.
Example callreturns →
Link one or more tickets to a parent (epic). Stories become children of the epic.
Takes no parameters.
Example callreturns →
Remove parent relationship from one or more tickets.
Takes no parameters.
Example callreturns →
Get the movement history for a ticket.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Flowboards costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 95 / 100
Release 1.0.3 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score95
Findings3 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digest7ce42f53ac5f3a290313f88ae2f009bc9a45187ccf09bdaba2c1b0700650efea
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (38 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_bins | no tags | |
| get_bin | no tags | |
| create_bin | no tags | |
| update_bin | no tags | |
| list_boards | no tags | |
| get_board | no tags | |
| add_comment | no tags | |
| list_comments | no tags | |
| get_comment | no tags | |
| update_comment | no tags | |
| delete_comment | no tags | |
| list_flows | no tags | |
| get_flow | no tags | |
| list_flow_tickets | no tags | |
| list_flow_moves | no tags | |
| list_ticket_types | no tags | |
| list_custom_fields | no tags | |
| list_users | no tags | |
| get_user | no tags | |
| invite_user | no tags | |
| list_user_groups | no tags | |
| search_tickets | no tags | |
| list_webhooks | no tags | |
| create_webhook | external-sink | |
| delete_webhook | external-sink | |
| test_webhook | external-sink | |
| create_ticket | no tags | |
| get_ticket | no tags | |
| list_tickets | no tags | |
| update_ticket | no tags | |
| move_ticket | no tags | |
| delete_ticket | no tags | |
| delete_tickets | no tags | |
| archive_tickets | no tags | |
| restore_tickets | no tags | |
| link_to_parent | no tags | |
| unlink_from_parent | file-write | |
| list_ticket_moves | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7ce42f53ac5f3a29
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.3 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.3
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Flowboards in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.