oflow-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@oflow-mcplist available workflow templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
oflow-mcp
Agent-native workflow kernel. 工作流不必只能是 Dify、n8n 或扣子。
oflow-mcp is a workflow-only MCP server. It treats workflow as an open execution protocol for AI Agents: text-defined, versionable, checkpointed, recoverable, and callable through MCP tools.
Product positioning
Traditional workflow platforms often center on visual canvases, proprietary node graphs, and hosted platform state. oflow-mcp starts from a different premise:
Agent native: prompts, outputs, checkpoints, and step state are first-class workflow concepts.
Text is the source of truth: workflows are
flow.yaml + prompts/*.md, so they can be reviewed, diffed, versioned, and reused.Verifiable execution: each step can require outputs, natural confirmations, deterministic checks, and persisted state.
Local-first kernel: the first version runs on MCP + filesystem; UI, connectors, triggers, remote execution, and enterprise governance can layer on top later.
Replacement path, not a plugin: the long-term goal is to replace the core capabilities of general workflow tools such as Dify, n8n, and Coze/扣子, starting with the execution kernel.
Related MCP server: A2CR
Non-goals for the first release
This first release intentionally excludes:
TAPD, Confluence, GitLab, CI, or IM integrations
memory, inbox, init, or instructions tools from
flow-mcpvisual canvas UI
database storage
multi-tenant permissions
Install
npm install
npm run buildStart
npm startMCP configuration example:
{
"mcpServers": {
"oflow-mcp": {
"command": "node",
"args": ["/path/to/oflow-mcp/dist/index.js"],
"env": {
"OFLOW_MCP_FLOWS_DIR": "/path/to/oflow-mcp/flows",
"OFLOW_MCP_DATA_DIR": "/tmp/oflow-mcp-instances"
}
}
}
}Environment variables
Variable | Default | Description |
|
| Base data directory |
|
| Workflow template directory |
|
| Workflow instance directory |
Tools
oflow-mcp exposes only workflow tools:
Tool | Description |
| List available templates |
| Get template details |
| Start a workflow instance |
| Get current step and rendered prompt |
| Complete current step and advance |
| Show full instance status |
| List instances |
| Bind alias to an instance |
| Override one step prompt for one instance |
| Create a template from YAML-like data and prompts |
No flow_memory_*, flow_inbox_*, flow_init, TAPD, or Confluence tools are exposed.
Template structure
flows/
basic-dev/
flow.yaml
prompts/
analyze.md
design.md
verify.mdMinimal flow.yaml:
name: basic-dev
description: Minimal Agent-native development workflow
params:
change_name:
type: string
required: true
steps:
- id: analyze
name: Analyze
checkpoint:
required_outputs:
analysis_summary:
type: string
min_length: 20
conditions:
- natural: analysis_summary has been produced
check: outputs.analysis_summary != null AND len(outputs.analysis_summary) > 20
next: design
- id: design
name: Design
next: nullPrompt variables:
{{change_name}}reads workflow params.{{steps.analyze.outputs.analysis_summary}}reads prior step outputs.Unresolved variables are left unchanged for debugging.
DSL support matrix
Feature | Status |
| Supported |
| Supported |
| Supported |
| Supported |
| Supported |
natural conditions | Supported |
deterministic | Supported subset |
| Supported |
loops | Not supported in first release |
optimization hints | Not supported |
worklog hooks | Not supported |
inbox/memory/external bindings | Not supported |
Supported check expressions:
outputs.foo != nulloutputs.foo == nulloutputs.foo == 'value'len(outputs.foo) > NAND,OR, parentheses
Unsupported expressions fail closed and do not mutate workflow state.
Example lifecycle
workflow_list_templatesworkflow_start:
{
"template": "basic-dev",
"params": { "change_name": "demo" },
"alias": "demo-run"
}workflow_currentwithdemo-runworkflow_advancewith required outputs and confirmed conditionsworkflow_statusContinue
workflow_advanceuntil completed
Development
npm install
npm run build
npm testCommon errors
Template not found: set
OFLOW_MCP_FLOWS_DIRor copy templates to~/.oflow-mcp/flows.Prompt not found: every step requires
prompts/<step_id>.md.Checkpoint validation failed: provide required outputs and confirmed conditions.
No branch matched: pass a
condition_resultmatching the branch keys innext.Alias already bound: choose another alias or use the existing instance ID.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/openpeng/flow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server