oflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OFLOW_MCP_HOME | No | Base data directory | ~/.oflow-mcp |
| OFLOW_MCP_DATA_DIR | No | Workflow instance directory | ~/.oflow-mcp/instances |
| OFLOW_MCP_FLOWS_DIR | No | Workflow template directory | ~/.oflow-mcp/flows |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workflow_list_templatesA | List available workflow templates. |
| workflow_get_templateA | Get workflow template details and step summary. |
| workflow_startB | Start a workflow instance from a template. |
| workflow_currentA | Get the current workflow step and rendered prompt. ID may be an instance id or alias. If omitted, uses the most recently active instance. |
| workflow_advanceB | Complete the current step and advance the workflow after checkpoint validation. |
| workflow_statusC | Show full workflow instance status. |
| workflow_list_instancesA | List workflow instances, optionally filtered by status and template. |
| workflow_bindB | Bind an alias to a workflow instance. |
| workflow_override_promptB | Override a step prompt for one workflow instance only. |
| workflow_create_templateB | Create a workflow template by writing flow.yaml and prompts/*.md. |
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 10 tools
Each tool targets a distinct operation: creation, starting, advancing, binding, querying, and overriding. No two tools have overlapping purposes.
All tools use the consistent 'workflow_verb_noun' pattern in snake_case, making the purpose clear and predictable.
With 10 tools, the surface is well-scoped for managing workflow templates and instances, covering all essential operations without unnecessary bloat.
Core CRUD and lifecycle operations are present (create, start, advance, status). Missing delete or stop operations for templates/instances is a minor gap, but the main workflows are covered.