MCP.Market

Workflow MCP server

by Juliusolsson05·io.github.Juliusolsson05/workflow-mcp·v1.1.0·3 stars

Session-bound Docker workflow server through Codex. State is discarded with the container.

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed Workflow MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Workflow MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Workflow MCP compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 35% of 1,119 Developer tools servers
GitHub stars
3
more than 75% of 855 Developer tools servers

Install Workflow MCP in Claude Code, Cursor or VS Code

claude mcp add workflow-mcp -- docker run -i --rm docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855
Add to Cursor

What the publisher says

From the Workflow MCP repository's README, as published. We do not edit it. Read it on GitHub

workflow-mcp

Run Claude Code dynamic-workflow files through any agent provider — as a durable, resumable Model Context Protocol server.

workflow-mcp is a standalone runtime and MCP server that executes Claude Code dynamic workflow files — the JavaScript orchestration programs that fan out dozens or hundreds of agent calls and return a single result — without requiring Claude to run them.

The whole project hangs on one promise:

A workflow authored for workflow-mcp can be copied into

.claude/workflows/.js and run by a compatible Claude Code release

without changing the file — and a real Claude workflow file runs through this

runtime without any importer or translation step.

Everything that isn't portable — which provider executes the agents, its credentials, the durable run cache, MCP run IDs, and UI state — lives in the runtime, never inside the .js file.

Why it exists

Claude Code workflows are a strong primitive: the JavaScript owns the loops, branches, fan-out, and aggregation, while each agent() call owns the model reasoning and side effects — keeping hundreds of intermediate results out of the parent conversation. But out of the box they come with three constraints:

directory, and it does not survive as an independently controllable object.

  • Claude executes every agent node. There is no seam for another provider.
  • A run belongs to a Claude session. Its state lives inside that session

or resume a run.

  • There is no server surface. Other tools cannot discover, launch, follow,

workflow-mcp keeps the exact same workflow file and lifts those constraints: the same .js runs through a provider-neutral engine (Codex today), every run is a durable object that survives restarts, and any MCP-capable host can drive it over a stable set of tools.

How it works

Two kinds of portability are kept deliberately separate — MCP solves the first, the provider interface solves the second:

MCP-capable host
      │  workflow_list · workflow_run · workflow_run_events · …
      ▼
WorkflowService  +  durable event store   ← the long-lived owner of runs
      ▼
Claude-compatible JavaScript runtime       ← agent/parallel/pipeline/phase/…
      ▼
provider-neutral AgentProvider
      ├─ Codex SDK  (@openai/codex-sdk)
      ├─ fake       (deterministic tests)
      └─ future providers

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Workflow MCP: common questions

Is Workflow MCP server safe?
Mostly: it is graded B (73/100). Read the Workflow MCP safety report
How do I install Workflow MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Workflow MCP need an API key?
Yes. The registry entry asks for OPENAI_API_KEY.
Is Workflow MCP maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v1.1.0.
What can I use instead of Workflow MCP?
Servers from other publishers that do the same job: maintenant MCP server, Komodo MCP Server and Podman MCP server.
How does Workflow MCP compare with other Developer tools MCP servers?
safety score 73/100 (higher than 35% of 1,119 Developer tools servers); github stars 3 (more than 75% of 855 Developer tools servers). Full comparison.

Alternatives to Workflow MCP

Same job from other publishers: the closest match first, then the best rated.

  • maintenant
    Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.
    C
  • Komodo MCP Server
    MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
    B
  • Podman
    A Model Context Protocol (MCP) server for container runtimes (Podman and Docker)
    A
  • Docker MCP Server
    Manage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI.
    A
  • Homebutler
    Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.
    C