Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Expose declarative YAML-defined workflows as MCP tools over stdio
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"yaml-workflow": {
"command": "uvx",
"args": [
"yaml-workflow",
"serve-mcp",
"--dir",
"{workflow_dir}"
]
}
}
}在终端中运行这条命令
claude mcp add yaml-workflow -- uvx yaml-workflow serve-mcp --dir '{workflow_dir}'粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"yaml-workflow": {
"command": "uvx",
"args": [
"yaml-workflow",
"serve-mcp",
"--dir",
"{workflow_dir}"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"yaml-workflow": {
"type": "stdio",
"command": "uvx",
"args": [
"yaml-workflow",
"serve-mcp",
"--dir",
"{workflow_dir}"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 orieg 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.9.6)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Fomu MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.