Workflows Mcp Server
Store reusable YAML workflow playbooks on disk and let agents query or author them with a filesystem-backed MCP index.
Overview
io.github.cyanheads/workflows-mcp-server is a MCP server for the Build phase that stores, queries, and creates YAML workflow playbooks for LLM agents from a local directory.
What is this MCP server?
- Persist and query YAML workflow playbooks from a configurable WORKFLOWS_DIR
- Create new workflow definitions through MCP tools for LLM agents
- Filesystem watcher rebuilds index with WATCHER_DEBOUNCE_MS default 500
- Optional GLOBAL_INSTRUCTIONS_PATH for shared markdown guidance across playbooks
- Stdio server @cyanheads/workflows-mcp-server v0.1.1 via Bun
- Server version 0.1.1
- Default WORKFLOWS_DIR ./workflows-yaml
- Default WATCHER_DEBOUNCE_MS 500
Community signal: 32 GitHub stars.
What problem does it solve?
Ad-hoc prompt chains vanish between sessions, so your agent keeps reinventing the same multi-step shipping ritual.
Who is it for?
Builders who want git-friendly agent runbooks for recurring ship tasks across Claude Code, Cursor, or Codex.
Skip if: Teams needing visual DAG schedulers, cross-service cron orchestration, or compliance-heavy BPM without YAML discipline.
What do I get? / Deliverables
Named YAML playbooks stay versioned on disk and your agent can load the right workflow before coding, reviewing, or releasing.
- Searchable index of YAML workflow playbooks on disk
- New or updated workflow YAML files created via agent tools
- Consistent global instructions referenced across workflows
Recommended MCP Servers
Journey fit
Repeatable agent procedures belong in build once you are codifying how your assistant ships features, not just one-off prompts. Agent-tooling subphase covers MCP servers that extend what your coding agent can orchestrate beyond single-turn chat.
How it compares
File-backed agent workflow library via MCP, not a cloud CI platform or a single static SKILL.md file.
Common Questions / FAQ
Who is io.github.cyanheads/workflows-mcp-server for?
Solo builders and small agent-first teams who want durable YAML workflows their MCP client can list and invoke.
When should I use io.github.cyanheads/workflows-mcp-server?
Use it when you are formalizing repeat agent procedures—reviews, releases, research sweeps—and want them indexed from a workflows folder.
How do I add io.github.cyanheads/workflows-mcp-server to my agent?
Install @cyanheads/workflows-mcp-server, configure stdio with Bun start:stdio, set WORKFLOWS_DIR to your YAML root, and optionally GLOBAL_INSTRUCTIONS_PATH and MCP_LOG_LEVEL.