Flow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| nvim | No | Path to a private same-user Neovim socket passed via --nvim for the reverse editor bridge. | |
| config | No | Path to an operator-reviewed TOML file passed via --config; explicitly approves loading that configuration. | |
| trusted | No | Set to "true" to include --trusted and enable project edits and explicitly configured named checks; default is read-only. | false |
| workspace | Yes | Absolute path to the project workspace passed via --workspace. Rose appends this flag for the MCP server. | |
| editor-timeout | No | Editor request timeout in seconds passed via --editor-timeout (0.1–660). | 120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Trusted workspace named checks only. Missing checks never verify.
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 |
|---|---|
| flow_runC | Bounded local planner/coder/reviewer run with real verification |
| flow_statusC | Local health, configured models/checks, editor capabilities |
| flow_checkC | Run operator-configured named checks; never arbitrary argv |
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 3 tools
flow_run (planner/coder/reviewer pipeline) and flow_check (named operator checks) are distinguished by their descriptions, though both perform 'verification-like' work and could be confused in edge cases. flow_status is clearly separate as a read-only info tool.
All three tools share a clean flow_ prefix with snake_case, which is predictable. Minor quibble: run and check are verbs while status is a noun, but the pattern remains easy to read.
Three tools is on the thin side for a workflow orchestrator; run/status/check covers the basics but feels like a minimal surface. It is borderline rather than mismatched, given the focused purpose.
Core lifecycle (execute a run, inspect status, run checks) is present, but there is no way to discover available check names, cancel an in-flight run, or retrieve prior run results/logs. These are notable gaps that could cause agent dead ends.