A
licenseB
qualityC
maintenanceEnables MCP-compatible clients to manage AI agent teams, including agents, Kanban issues, projects, goals, approvals, budgets, and raw API access.
30
MIT
flow-team-mcp
Related Servers
Alternatives to flow-team-mcp
No user-submitted related servers found.
Related Servers
kickflow MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables interaction with the kickflow workflow management API through MCP, supporting comprehensive operations for tickets, approvals, users, teams, workflows, comments, and organizational management.488 npm4MIT- AlicenseAqualityCmaintenanceEnables MCP hosts to call the Teamline API for user authentication, task listing, creation, completion, and webhook management.6MIT
- AlicenseAqualityDmaintenanceEnables test execution and management through MCP clients, allowing retrieval of projects, listing tests, executing tests with browser selection, and monitoring results.68 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the hosted PacedLoop API to manage workflows and monitor process runs. It provides tools for workflow CRUD operations, run execution management, and access to detailed performance analytics within MCP-capable clients.-
- AlicenseNot gradedqualityBmaintenanceEnables API development directly from MCP clients by creating and editing collections, running requests through the real CLI, generating documentation, and starting mock servers.87 npmMIT
TDQS
B3/5.0
Scored across 11 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityNo data
ResponsivenessNo issues