Workflow Server

Structured workflows for AI agents

Workflow Server is an MCP server that guides agents through multi-step workflows. You describe a goal in plain language; the agent follows a defined process and pauses at checkpoints when your decision matters.

The workflow model A chain of five stages connected by arrows: a user goal is fulfilled by a workflow, a workflow is made of activities, activities apply techniques, and techniques invoke tools. User goal Workflow Activities Techniques Tools “implement issue #42” the overall process, e.g. work-package phases: plan, implement, review, validate markdown definitions of a capability operations the agent invokes
The workflow model. A user goal is fulfilled by a workflow; the workflow is made of activities (its phases); each activity applies techniques (markdown definitions of a capability, with optional rules); and techniques invoke tools — the operations the agent performs.

How it works

For users

You speak in natural language. The agent matches your request to a workflow, works through its phases, and stops at checkpoints when you need to decide something. You never manage tool names or session tokens yourself.

  1. Install and connect. Build the server and register it with your MCP client.
  2. Add the IDE rule. One always-applied rule makes the agent call discover first.
  3. Run or resume. Start, resume, or end a workflow in plain language.
  4. Answer checkpoints. When the run pauses, pick an option. The workflow cannot advance until you respond.

Setup, the bootstrap rule, and example phrases are in Getting started.

For agent implementers

The agent follows a bootstrap procedure returned by discover — you do not call MCP tools yourself; the IDE rule routes workflow requests here.

Tool reference (16 tools, generated from source). Protocol for call order, checkpoints, errors, and reference delivery. Workflows for orchestrator vs worker roles.

The pieces

Your MCP client hosts the agent. The agent reaches the workflow-server through MCP; the server reads workflow definitions and owns session state in your project's workspace.

System layers Agents reach the server through sixteen MCP tools. Below the tool surface sit the enforcement layers, which consult workflow definitions read from the workflows directory and the session state persisted in the workspace. Agents (orchestrators and workers) MCP tool surface 16 tools across six concerns Enforcement and resolution fidelity layers · technique bundles Workflow definitions workflows/ (read) Session state session.json + .session-token in your workspace MCP reads owns
Agents only ever see the tool surface; the server validates every call against the workflow definition and persists canonical session state under .engineering/artifacts/planning/. Setup steps are in Getting started.

What a run looks like

A session moves through the workflow's activities in order, pausing at checkpoints for your decisions.

A session timeline A timeline of session stages. Each activity follows its steps; steps apply techniques; techniques consult linked resources (detail shown once below the first activity). Checkpoints pause the run for your decision. session starts activity e.g. plan checkpoint your decision activity e.g. implement complete step(s) technique(s) resource(s) follows apply consult
Activities run in sequence; each activity follows its step(s), steps apply techniques, and techniques consult linked resources — shown once below the first activity. Checkpoints (rounded) pause the run for your decision. See Checkpoints.

Where to start

Match your question to a page. This site is the browsable view; markdown in the repository is what you edit when you change the docs.

Your questionRead this
I am new — where do I begin?Getting started → Definitions
What is this project?The pieces on this page or README (source)
How do I install and connect the server?Getting started
How do I deploy .engineering to my project?Getting started — step 2
How do I wire the IDE bootstrap rule?Getting started
How do I run or resume a workflow?Getting started — example phrases
What are workflows, sessions, and checkpoints?Definitions · Checkpoints
What tools does the server expose?Tool reference and API reference (source)
What do errors and warnings mean?Protocol
How do I author workflow definitions?Specifications · Schema reference
How is the system designed?Architecture overview and the model pages linked from it
How is the server implemented?Design overview — module map, request path, session store, quality gates
What keeps agents faithful to a workflow?Workflow fidelity
How do techniques declare protocol and bindings?Technique protocol (source)
How do I contribute to the server?Server anatomy and Development guide (source)
Where does new documentation belong?Documentation system (source)