workflow_listLABSCO SUMMARY
Playbooks live as files you can review in a pull request, not as prompt text pasted into a chat.
workflow_get returns the workflow together with the global instructions in the same response, so the agent never needs a second call to know how to run it. The filesystem watcher rebuilds the index on any edit, which means you can change a playbook in your editor and the running server picks it up.
What it is
A workflow library served over MCP. It indexes a directory of YAML playbooks by name and version at startup, watches the filesystem for changes, and hands complete workflow definitions to an agent on request.
What you get
- workflow_list — list permanent workflows, filtered by keyword, category or tags; set includeTools to surface the server/tool pairs each workflow depends on
- workflow_get — fetch a complete workflow by name, semver-aware, with the global instructions document already attached
- workflow_create — write a new permanent workflow, one file per name and version, so revisions coexist
- workflow_create_temp — write a throwaway one-shot workflow that is retrievable but stays out of list results
- workflow_delete — remove a permanent workflow by name and optional version
- Typed errors with reason codes such as not_found, version_not_found and already_exists, so a caller can branch instead of parsing messages
- Template placeholders come back verbatim — the server never interpolates them
Requirements
No API keys. Bun v1.3.0 or higher, or Node.js v24+, and a directory of YAML workflow files — the repository ships a seed library you can start from. Point WORKFLOWS_DIR at it; GLOBAL_INSTRUCTIONS_PATH and WATCHER_DEBOUNCE_MS are optional overrides. Runs over stdio or Streamable HTTP, and ships as a Docker image.
Setup effort
One command — bunx @cyanheads/workflows-mcp-server@latest
USE CASES
Finding the right playbook for the task
Filter the library by keyword, category or tag, and see which servers and tools each candidate needs before picking one.
Running a stored procedure end to end
Fetch the latest version by name and get the global instructions in the same response.
Turning a session that worked into a reusable playbook
Write the steps out as a new versioned workflow so the next run does not rediscover them.
Scaffolding a one-off plan
Write a throwaway workflow for this session that stays out of the library listing.
Retiring an old revision
Delete a specific version by name while leaving the others in place.
5 tools
Listed in project docs. Your client may show a different list.
workflow_getworkflow_createworkflow_create_tempworkflow_deleteBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
bunx on PATH
INSTALLATION
Connect your client
Server setup
bunx @cyanheads/workflows-mcp-server@latestMCP Clients
Claude Desktop
https://github.com/cyanheads/workflows-mcp-server/releases/latest/download/workflows-mcp-server.mcpbCursor
https://cursor.com/en/install-mcp?name=workflows-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBjeWFuaGVhZHMvd29ya2Zsb3dzLW1jcC1zZXJ2ZXIiXX0=VS Code
https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22workflows-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40cyanheads%2Fworkflows-mcp-server%22%5D%7D