workflow-orchestrator

workflow-orchestrator is an MCP server for Claude Code from daffy0208/ai-dev-standards. Its token cost is not measured, scanned A, original, MIT.

A local MCP server for running and coordinating workflows, which are ordered sequences of automated tasks.

In plain words
What is it for?
It helps run workflows through the listed Node.js server, but the supplied description does not specify the available workflow operations.
Why use it?
It gives an agent a configured workflow engine instead of requiring each workflow step to be managed separately.

MCP server for Claude Code

Written for Claude Code: installed under .claude/. Also seen: listed in a Claude config.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/david/.claude/plugins/marketplaces/claude-code-plugins-plus/plugins/mcp/workflow-orchestrator/dist/servers/workflow-engine.js.

One of 54 entries in claude_desktop_config.json — they are configured in one file and arrive together.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workflow-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/mcp/daffy0208/ai-dev-standards/workflow-orchestrator.svg)](https://agentmods.dev/mcp/daffy0208/ai-dev-standards/workflow-orchestrator)
Your own site
<a href="https://agentmods.dev/mcp/daffy0208/ai-dev-standards/workflow-orchestrator"><img src="https://agentmods.dev/badge/mcp/daffy0208/ai-dev-standards/workflow-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

workflow-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/claude_desktop_config.json · 8 lines

What it actually says

{
  "workflow-orchestrator": {
    "command": "node",
    "args": [
      "/home/david/.claude/plugins/marketplaces/claude-code-plugins-plus/plugins/mcp/workflow-orchestrator/dist/servers/workflow-engine.js"
    ]
  }
}
Same file

What else claude_desktop_config.json configures

This page is one entry in a file that holds 54. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 8 lines scan A 75eed7e04517

Subscribe to this mod's changes

workflow-orchestrator is an MCP server published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.