Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

YAML Workflow

by oriegversion 0.9.6i★ –iRuns on your computer
Registry nameio.github.orieg/yaml-workflow

Install

Overview

Description from the maker (original English)

Expose declarative YAML-defined workflows as MCP tools over stdio

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "yaml-workflow": {
      "command": "uvx",
      "args": [
        "yaml-workflow",
        "serve-mcp",
        "--dir",
        "{workflow_dir}"
      ]
    }
  }
}

Run this in your terminal

claude mcp add yaml-workflow -- uvx yaml-workflow serve-mcp --dir '{workflow_dir}'

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yaml-workflow": {
      "command": "uvx",
      "args": [
        "yaml-workflow",
        "serve-mcp",
        "--dir",
        "{workflow_dir}"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "yaml-workflow": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "yaml-workflow",
        "serve-mcp",
        "--dir",
        "{workflow_dir}"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account orieg, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32466 servers in this category
  • Published to the registry more recently than 25% of the other 32466 servers in this category
  • Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is YAML Workflow safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.6) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

YAML Workflow

A lightweight workflow engine for CI/CD pipelines, data processing, and DevOps automation. Define reproducible, version-controlled workflows in YAML — run them locally, in CI, or on any machine with Python installed.

Why yaml-workflow?

Most workflow tools require servers, databases, and complex infrastructure. yaml-workflow takes a GitOps approach — workflows are plain YAML files, version-controlled alongside your code:

yaml-workflowAirflow / Prefect / Dagster
Setuppip install yaml-workflowServer, database, scheduler, workers
ConfigurationPlain YAML filesPython DAGs + infrastructure config
Dependencies2 (PyYAML, Jinja2)50+ packages, Docker, PostgreSQL
Use caseLocal automation, scripts, CI/CD, data pipelinesEnterprise orchestration at scale
Learning curveMinutesHours to days
StateFile-based, resumableDatabase-backed

Choose yaml-workflow when you need:

  • Simple task automation without infrastructure overhead
  • Reproducible pipelines defined in version-controlled YAML
  • Batch processing with parallel execution
  • State persistence and workflow resume after failures
  • A lightweight alternative to shell scripts with better error handling
  • GitOps-friendly pipelines that live in your repo alongside the code
  • A single tool that runs the same pipeline locally and in CI

Features

  • YAML-driven workflow definition with Jinja2 templating
  • Multiple task types: shell, Python, file, template, HTTP, batch
  • Workflow composition via imports — reuse steps across workflows
  • Plugin system via entry points — pip install yaml-workflow-myplugin
  • Watch mode — --watch to re-run on file changes
  • Dry-run mode to preview without executing
  • Workflow visualization (ASCII branching DAG and Mermaid)
  • Parallel execution with configurable worker pools
  • State persistence and resume capability
  • Retry mechanisms with configurable strategies
  • Namespaced variables (args, env, steps, batch)
  • Flow control with custom step sequences and conditions
  • Extensible task system via @register_task decorator
  • Parallel step execution via depends_on — run independent steps concurrently
  • Secrets validation — fail fast if required environment variables are missing
  • Structured output (--format json) for CI integration and scripting
  • MCP server — expose workflows as AI agent tools (pip install yaml-workflow[mcp])
  • Web dashboard — monitor runs and trigger workflows (pip install yaml-workflow[serve])
  • GitHub Action — run workflows in CI with uses: orieg/yaml-workflow@v0.9.3

Use Cases

  • CI/CD pipelines — multi-step build, test, deploy workflows in YAML
  • Data processing — batch ETL pipelines with retry and resume on failure
  • DevOps automation — infrastructure tasks with secrets management and notifications
  • AI/LLM pipelines — orchestrate API calls with auth, retry, and batch processing
  • Local automation — replace shell scripts with reproducible, parameterized workflows

Quick Start

# Install (isolated CLI — recommended)

pipx install yaml-workflow # Core CLI pipx install 'yaml-workflow[all]' # + web dashboard + MCP server

Or with pip

pip install yaml-workflow

Initialize example workflows

yaml-workflow init

Run a workflow with parameters

yaml-workflow run workflows/hello_world.yaml name=Alice

Example workflow (hello_world.yaml):

name: Hello World

description: A simple greeting workflow

params: name: type: string default: World

steps:

  • name: create_greeting task: template inputs: template: "Hello, {{ args.name }}!" output_file: greeting.txt
  • name: show_greeting task: shell inputs: command: cat greeting.txt
Visualize workflows
yaml-workflow visualize workflows/data_pipeline.yaml
  Workflow: Data Pipeline

┌─────────────────┐ │ detect_format │ │ python_code │ └─────────────────┘ │ ▼ ┌────────────────┐ ┌────────────────┐ ┌────────────────┐ ┌────────────────┐ │ process_json │ │ process_csv │ │ process_xml │ │ handle_unknown │ │ shell │ │ shell │ │ shell │ │ shell │ └────────────────┘ └────────────────┘ └────────────────┘ └────────────────┘ │ ▼ ┌─────────────────┐ │ generate_report │ │ python_code │ └─────────────────┘

Adjacent conditional steps are automatically grouped as branches. Use --format mermaid to export for docs or GitHub rendering.

Dry-run mode

Preview what a workflow would do without executing anything:

yaml-workflow run workflows/hello_world.yaml name=Alice --dry-run
[DRY-RUN] Workflow: Hello World

[DRY-RUN] Steps: 2 to execute

[DRY-RUN] Step 'create_greeting' — task: template — WOULD EXECUTE template: Hello, Alice! output_file: greeting.txt [DRY-RUN] Step 'show_greeting' — task: shell — WOULD EXECUTE command: cat greeting.txt

[DRY-RUN] Complete. 2 step(s) would execute, 0 would be skipped. [DRY-RUN] No files were written. No tasks were executed.

Workflow composition

Reuse steps across workflows with imports:

# main.yaml

imports:

  • ./shared/logging_steps.yaml
  • ./shared/common_params.yaml

steps:

  • name: my_step task: shell inputs: command: echo "runs after imported steps"

Imported steps are prepended. Imported params provide defaults that the main workflow can override. Supports transitive imports with circular detection.

Parallel Steps

Run independent steps concurrently with depends_on:

steps:
  • name: fetch_api task: http.request inputs: {url: "https://api.example.com/data"}
  • name: fetch_db task: python_code inputs: code: "result = query_database()"
  • name: merge task: python_code depends_on: [fetch_api, fetch_db] inputs: code: | api_data = steps"fetch_api" db_data = steps"fetch_db" result = {"merged": True}
Watch mode

Automatically re-run on file changes during development:

yaml-workflow run workflows/hello_world.yaml name=Alice --watch

Monitors the workflow file and all imported files. Press Ctrl+C to stop.

GitHub Actions

Run workflows in CI with the yaml-workflow action:

- name: Run pipeline

uses: orieg/yaml-workflow@v0.9.3 id: pipeline with: workflow: workflows/deploy.yaml params: | env=production version=1.2.0 format: json

  • name: Use results run: echo '${{ steps.pipeline.outputs.result }}'
Docker & Kubernetes

Run anywhere without installing Python:

# Run a workflow in Docker

docker run --rm -v $(pwd)/workflows:/app/workflows \ ghcr.io/orieg/yaml-workflow run /app/workflows/pipeline.yaml

Start the web dashboard

docker run -p 8080:8080 -v $(pwd)/workflows:/app/workflows \ ghcr.io/orieg/yaml-workflow

Deploy on Kubernetes with the Helm chart:

helm install my-workflows ./helm/yaml-workflow \

--set-file workflows.files.pipeline\\.yaml=workflows/pipeline.yaml

Compatible with ArgoCD (GitOps) and Argo Workflows. See the Kubernetes guide.

More commands
# List available workflows

yaml-workflow list

Validate a workflow (with JSON output for CI)

yaml-workflow validate workflows/hello_world.yaml --format json

Resume a failed workflow

yaml-workflow run workflows/hello_world.yaml --resume

Structured output for scripting

yaml-workflow run workflows/pipeline.yaml --format json --output results.json

Documentation

Full documentation is available at [orieg.github.io/yaml-workflow](https://orieg.github.io/yaml-workflow/).

Contributing

Contributions are welcome! See the Contributing Guide for development setup and guidelines.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Ask PopNx