flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_MCP_REQ_PATH | Yes | The request path used by flow-mcp to locate .runs directory |
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 |
|---|---|
| flow.finishA | End the current business action with an explicit success or failure conclusion. |
| flow.pauseA | Pause the current business action while waiting for a user, dependency, or external system. |
| flow.resumeB | Mark a waiting business action as ready for continued scheduling. |
| flow.rewindC | Request a rewind to the last stable point or an authorized checkpoint before re-execution. |
| flow.abortC | Terminate the current business flow without treating it as business failure. |
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 5 tools
Each tool targets a distinct action in the flow lifecycle: abort (terminate without failure), finish (end with success/failure), pause (wait), resume (continue), rewind (go back to checkpoint). No overlap.
All tool names are single lowercase verbs (flow.abort, flow.finish, etc.), following a consistent verb-only pattern that describes the action clearly.
Five tools is appropriate for managing business flow lifecycle. It covers the essential operations without being excessive or too sparse.
The set covers key flow actions (abort, finish, pause, resume, rewind) but is missing a 'start' or 'initiate' tool, assuming flows are started externally. Minor gap for a complete lifecycle.