Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Expose declarative YAML-defined workflows as MCP tools over stdio
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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}'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.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account orieg, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.9.6) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
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.
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.
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-workflow | Airflow / Prefect / Dagster | |
|---|---|---|
| Setup | pip install yaml-workflow | Server, database, scheduler, workers |
| Configuration | Plain YAML files | Python DAGs + infrastructure config |
| Dependencies | 2 (PyYAML, Jinja2) | 50+ packages, Docker, PostgreSQL |
| Use case | Local automation, scripts, CI/CD, data pipelines | Enterprise orchestration at scale |
| Learning curve | Minutes | Hours to days |
| State | File-based, resumable | Database-backed |
Choose yaml-workflow when you need:
imports — reuse steps across workflowspip install yaml-workflow-myplugin--watch to re-run on file changesargs, env, steps, batch)@register_task decoratordepends_on — run independent steps concurrently--format json) for CI integration and scriptingpip install yaml-workflow[mcp])pip install yaml-workflow[serve])uses: orieg/yaml-workflow@v0.9.3# Install (isolated CLI — recommended)
pipx install yaml-workflow # Core CLI pipx install 'yaml-workflow[all]' # + web dashboard + MCP server
pip install yaml-workflow
yaml-workflow init
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:
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.
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.
Reuse steps across workflows with imports:
# main.yaml
imports:
steps:
Imported steps are prepended. Imported params provide defaults that the main workflow can override. Supports transitive imports with circular detection.
Run independent steps concurrently with depends_on:
steps:
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.
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
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
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.
# List available workflows
yaml-workflow list
yaml-workflow validate workflows/hello_world.yaml --format json
yaml-workflow run workflows/hello_world.yaml --resume
yaml-workflow run workflows/pipeline.yaml --format json --output results.json
Full documentation is available at [orieg.github.io/yaml-workflow](https://orieg.github.io/yaml-workflow/).
Contributions are welcome! See the Contributing Guide for development setup and guidelines.
This project is licensed under the MIT License - see the LICENSE file for details.