@flowmaster-io/mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@flowmaster-io/mcplist my open tasks"
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.
@flowmaster-io/mcp
Connect an AI assistant to your Flow Master workspace.
Once configured, assistants like Kiro, Claude Desktop and Cursor can look up your projects, open and update tasks and tickets, move work along your boards, link related items, and read or write comments — using your own Flow Master account and permissions.
The server runs locally on your machine and talks to your Flow Master installation over HTTPS.
Requirements
Node.js 20 or newer
A Flow Master account
Your workspace URLs, available from your Flow Master administrator
Related MCP server: toflow MCP Server
Setup
Add the server to your MCP client's configuration:
{
"mcpServers": {
"flowmaster": {
"command": "npx",
"args": ["-y", "@flowmaster-io/mcp"],
"env": {
"FLOWMASTER_API_URL": "https://api.example.com",
"FLOWMASTER_WEB_URL": "https://app.example.com"
}
}
}
}Replace both URLs with the ones for your workspace.
Then sign in once:
FLOWMASTER_WEB_URL=https://app.example.com npx -y @flowmaster-io/mcp loginYour browser opens, you sign in the way you normally do, and the session is
stored at ~/.flowmaster/mcp.json with owner-only permissions. Restart your MCP
client afterwards.
What the assistant can do
Projects and tasks:
Tool | What it does |
| Find a project by name or code |
| Read one project by id |
| Read the tasks in one project, with their descriptions and tags |
| Read one task by id |
| Open a task in a project |
| Change a task's title, description, priority, due date or tags |
Tickets:
Tool | What it does |
| Read tickets with their descriptions and tags |
| Read one ticket by id |
| Open a support ticket |
| Change a ticket's title, description, priority, due date or tags |
Boards:
Tool | What it does |
| See which stages an item is allowed to move to next |
| Move an item to another stage on its board |
Relationships, tags and comments:
Tool | What it does |
| Record that one item blocks, depends on or belongs under another |
| See what an item is linked to, and which way round |
| Remove a relationship |
| List tags with their kind, so the assistant can assign the right one |
| Comment on a task or ticket |
| Read the comments on an item |
Everything runs as you. The assistant cannot see or change anything your account cannot already see or change.
Read-only tools are marked as such, so most clients run them without asking. Tools that create or change something are marked as writes, and clients will normally ask you to confirm before they run.
Lists return at most 25 items per call, and report how many matched in total, so the assistant can ask for the next page when it needs more.
Tags are how Flow Master classifies work, and the kind tells the assistant what a tag means — for example a partner space has its own tag. Ask the assistant to tag something and it will look the tag up rather than guess. Setting tags replaces the existing ones, so ask for the full set you want.
Moving work along a board goes through the flow, not around it: the assistant asks which stages an item may move to and picks from that answer, so a move your flow does not allow simply is not offered. Say something like "this one is done, put it in review" and it will find the stage. A move can trigger the automations set up on the stage it lands in, exactly as if you had dragged the card yourself.
Relationships record how work fits together: what blocks what, what depends on what, and what sits under a parent item. Say "this one can't start until the API work is done" and the assistant records it as a dependency you can see in the app.
After a create or update, only the fields that were written come back. Ask the assistant to read the item again to see its stored state, including tags.
Commands
Command | Purpose |
| Start the server. Your MCP client runs this for you. |
| Sign in through the browser |
| Sign out and delete the stored session |
| Show who is currently signed in |
Configuration
Variable | Required | Purpose |
| yes | Your Flow Master API URL |
| for | Your Flow Master web address |
| no | Use an existing access token instead of signing in |
Neither URL has a default. If one is missing the server stops at startup with a message naming it, rather than quietly failing later.
Troubleshooting
"FLOWMASTER_API_URL is not set" — the variable is missing from your client
configuration. Check the env block above.
"Not signed in" — run the login command, then restart your MCP client.
"Session expired" — sessions last 30 days. Run login again.
The assistant cannot see a project or ticket — your Flow Master account does not have access to it, or the relevant module is turned off for your organization. Ask your administrator.
A stage the assistant expected is not offered — the flow does not allow that move from the item's current stage. Move it in the app, or adjust the flow.
Sign-in works on one machine but signs you out on another — a Flow Master account holds one assistant session at a time. Signing in on a second machine ends the first.
Privacy
The server sends only what a tool call needs, and only to the Flow Master installation you configured. Your session token stays on your machine. Nothing is sent anywhere else.
Content the assistant reads from Flow Master, such as comments, is passed to whichever AI provider your MCP client uses. Your client's own privacy terms cover that step.
Support
Contact your Flow Master administrator, or open an issue at https://github.com/flow-master-io/mcp/issues
This server cannot be deployed
Maintenance
Related MCP Connectors
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
- OpenOakOAuthorg.openoak
Secure AI access to OpenOak tasks, notes, and Kanban boards.
Connect AI assistants to Stellary projects, boards, documents, and governed agent workflows.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with your Productboard workspace, allowing features, products, notes, objectives, key results, and releases management.20MIT

toflow MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access toflow.ai workspace for prospecting, multi-channel outreach (email, LinkedIn, WhatsApp), sequences, enrichment, CRM, and AI automations.6MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Backlog projects, issues, wikis, and pull requests via natural language, with multi-space support and secure OAuth authentication.MIT

Workel MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to access and manage a Workel workspace through MCP tools, reading projects, tasks, comments, events, and members, and optionally creating or updating tasks, comments, and events when write scopes and local consent are enabled.9 npmMIT