DevFlow MCP Server

devflow_init

Initialize a DevFlow work session: validates and locks the flow, creates an agent session, and returns context with tasks, feedback, allowed actions, and next step. Call first to enable other tools.

Instructions

Initialize a DevFlow work session for a flow.

MUST be called before any other tools (except flow_list and flow_create). Without devflow_init, all tools are blocked.

What it does:

Validates and loads the flow
Locks the flow for this agent (exclusive)
Creates an agent session for tracking
Returns full context: flow details, feedback, tasks, allowed actions, next step

Call this at the start of every work session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devflow_init"
  }
}

Input Schema

Name	Required	Description	Default
`flowId`	No	The flow ID to work on. If omitted, shows available projects and flows.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.35.0Jun 7, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses key behaviors: validates and loads flow, locks it exclusively, creates a session, returns full context. With no annotations, it covers essential actions, though it could mention handling of already-locked flows or session duration.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a clear one-liner, followed by a bullet list and a call to action. While detailed, every sentence adds value; minor trimming could improve conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately describes the return value (full context: flow details, feedback, tasks, etc.) and sets expectations for a session initialization tool. Covers prerequisite behavior and optional use of flowId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one optional parameter. The description adds meaning by explaining that omitting flowId shows available projects and flows, which clarifies the parameter's behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool initializes a DevFlow work session for a flow, using specific verbs like 'Initialize' and listing concrete actions (validates, locks, creates, returns). It distinguishes itself from sibling tools by noting it must be called before most others.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states it must be called before any other tools except flow_list and flow_create, and that all tools are blocked without it. Also advises calling at the start of every work session, providing clear when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server