flow-team-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_API_KEY | Yes | Flow OpenAPI 호출에 사용할 API Key입니다. | |
| FLOW_API_BASE_URL | No | Flow API base URL입니다. 테스트 또는 프록시 환경에서만 변경하세요. | https://api.flow.team |
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 |
|---|---|
| list_flow_endpointsC | Flow OpenAPI 문서에서 수집한 엔드포인트 목록을 조회합니다. |
| get_flow_endpointA | 엔드포인트 ID로 Flow OpenAPI 경로, HTTP 메서드, 문서 URL을 조회합니다. |
| flow_requestB | Flow OpenAPI를 호출합니다. FLOW_API_KEY 환경변수를 기본으로 사용하며, x-flow-api-key 헤더를 자동 추가합니다. |
| get_project_api_schemaC | 프로젝트 API의 Metadata, Request, Response, Error 문서 정보를 조회합니다. |
| list_projectsC | Flow 프로젝트 목록을 조회합니다. |
| list_participant_projectsB | 특정 사용자가 참여 중인 Flow 프로젝트를 조회합니다. |
| get_project_participantsC | Flow 프로젝트 참여자 목록을 조회합니다. |
| get_project_columnsC | Flow 프로젝트 컬럼 목록을 조회합니다. |
| get_project_status_columnsB | Flow 프로젝트 상태 컬럼 목록을 조회합니다. |
| create_projectD | Flow 프로젝트를 생성합니다. |
| add_project_participantsC | Flow 프로젝트에 참여자를 추가합니다. |
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 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.