flow-team-mcp
Related Servers
Alternatives to flow-team-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to manage AI agent teams, including agents, Kanban issues, projects, goals, approvals, budgets, and raw API access.30MIT

kickflow MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables interaction with the kickflow workflow management API through MCP, supporting comprehensive operations for tickets, approvals, users, teams, workflows, comments, and organizational management.754 npm4MIT- AlicenseAqualityDmaintenanceEnables MCP hosts to call the Teamline API for user authentication, task listing, creation, completion, and webhook management.6MIT
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to query and update projects, boards, and tasks with the user's permissions, including comments, checklists, time logging, dashboards, and evidence attachments.22MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to call Helm7's API operations through a hosted endpoint with browser-based OAuth sign-in, or via a locally built server authenticated with a scoped HELM7_API_KEY. Its interfaces are generated from a shared API catalogue so the MCP tools and SDK stay aligned.Apache 2.0
TDQS
Scored across 11 tools
Most tools have distinct purposes: listing vs fetching a single endpoint, project vs participant-specific project lists, and different column types. However, get_project_columns and get_project_status_columns could be confused, and list_projects vs list_participant_projects may overlap without careful reading.
The naming convention is predominantly verb_noun snake_case (get_, list_, create_, add_) which is predictable. The exception is flow_request, which does not follow the get/list pattern but still communicates its action clearly.
With 11 tools, the set is well-scoped for a Flow project management and API integration server. Each tool addresses a distinct need, and the count is within the ideal 3-15 range without feeling bloated or thin.
The server covers core project operations: listing/creating projects, managing participants, accessing columns, and handling API endpoints including schema, list, get, and invocation. Missing are update/delete for projects or participants, but these may be out of scope for the intended workflows.