Best for
- Developers using Claude Code who need DAG-based automation
- Teams that want deterministic, dependency-driven task execution
W
Workflow Orchestrator
Community
DAG-based workflow orchestration with parallel execution and run history
- Category
- Dev Tools #422 of 438
- Stars
- ★ 2.8k Very popular
- Transport
- stdio (local process)
- Runtime
- Node.js
- Credentials
- No credential needed
- License
- MIT
- Last commit
27FMRS · D
A community MCP server for DAG-based workflow orchestration, published in the Tons of Skills / Claude Code plugins marketplace. The manifest lists version 1.0.0, npm distribution, and stdio transport, but no individual tools are documented in the supplied source.
Strongest · Maintenance 10/20 Weakest · Documentation 3/20
Why each score
- Reliability 4/20
- Only the manifest (npm package, stdio, version 1.0.0) and a one-line marketplace description are supplied; no source, tool list, tests, or CI evidence for this server, so the init handshake and tool behavior cannot be verified. Static calibration caps reliability at 12 without execution evidence; with missing evidence and uncertainty rounded down, score 4.
- Security and permissions 5/20
- No red-line issues (malware, credential theft, unconfirmed destructive actions) are evident, but only manifest and catalog-level text exist; there is no documentation of credential handling, least privilege, network boundaries, or confirmation of dangerous operations. A workflow orchestrator may execute tasks, yet no security design is shown, so score 5 after deducting for missing evidence.
- Maintenance 10/20
- The repository is not archived, has an MIT license, and the README shows ongoing releases (v4.33.0), validators, and community contributors, indicating the marketplace is maintained; however, there is no server-specific commit history, release record, or issue-response evidence, so a mid-low score of 10 is appropriate.
- Documentation 3/20
- Evidence is limited to the manifest description and a one-line table entry in the marketplace README; there is no server-specific install, auth, tool-parameter, limits, cost, or troubleshooting documentation and no examples. Docs do not contradict capability but are barely usable, so score 3.
- Setup experience 5/20
- The manifest declares an npm package over stdio, and the repo README shows generic ccpi/plugin install commands, but there are no step-by-step instructions for this server, no client configuration example, and no platform compatibility verification. Static calibration caps setup at 15 and there is no execution evidence; uncertainty is rounded down to 5.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessRuns commands or code
Not for
- Teams needing real-time collaboration or human-in-the-loop decision tools
- Scenarios where a simpler linear script is sufficient
Required permissions
- Runs as a local stdio process via the npm package @claude-code-plugins-plus/workflow-orchestrator
- No explicit permission documentation is provided in the source
Risks and side effects
- Third-party community plugin — no official upstream maintainer
- MIT-licensed, but the code is not audited in this profile
- No server-specific security documentation in the source
Setup
Before you start
Runtime：Node.js
Install the ccpi CLI (pnpm add -g @intentsolutionsio/ccpi) and run ccpi install workflow-orchestrator, or use Claude Code's built-in /plugin marketplace add jeremylongshore/claude-code-plugins followed by /plugin install workflow-orchestrator@claude-code-plugins-plus. The npm package @claude-code-plugins-plus/workflow-orchestrator will run as a stdio MCP server.
Check that it works
After installing, check that the workflow-orchestrator server appears in your client's MCP server list, then ask it to run a simple parallel workflow to confirm its tools are available.
Troubleshooting
- Confirm the npm package @claude-code-plugins-plus/workflow-orchestrator is installed
- Ensure your MCP client supports stdio transport
- Check the repository's public wiki and production playbooks for MCP reliability guidance
Things to try
Once connected, you can ask your AI assistant things like:
- Create a workflow with parallel-executing tasks
- Run my workflow and show the run history
- Orchestrate a DAG workflow based on these dependencies
Use cases
Orchestrating multi-step workflows with task dependencies
Running independent tasks in parallel
Reviewing run history of past executions
Supported clients
Claude Code
Listed from the project's documentation, not tested by this site.
Overview
Workflow Orchestrator is an MCP server that implements directed-acyclic-graph (DAG) based workflow orchestration. It enables parallel task execution, dependency management between tasks, and keeps a run history of executed workflows. It is distributed as the npm package @claude-code-plugins-plus/workflow-orchestrator (v1.0.0) and communicates via stdio.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision ebea1067983c Data synced 2026-10-12 Read the FMRS scoring method