# Workflow MCP

Run Claude-compatible JavaScript workflows as Codex jobs inside Docker. The standalone setup suits projects that can discard container state when a run ends.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 5
- Author: Juliusolsson05
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Juliusolsson05/workflow-mcp/tree/HEAD/standalone
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/workflow-mcp

## What it does

Workflow MCP exposes Claude-compatible JavaScript workflow definitions as Codex-backed jobs over MCP. Docker provides the runtime and process isolation. In the `standalone` setup, the container runs with `--rm`, so its state goes away when the container exits. Jobs that need state to survive a run require a different lifecycle.

The setup needs Docker plus values for `OPENAI_API_KEY` and `WORKFLOW_MCP_CONCURRENCY`. For Claude Code, the install command starts the image pinned by digest; the provided configurations also cover Codex, Cursor, GitHub Copilot, and Gemini CLI. With this container mode, task state does not persist after the container stops.

## Requirements
- Needs: Docker
- Environment variables: `OPENAI_API_KEY`, `WORKFLOW_MCP_CONCURRENCY` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env OPENAI_API_KEY=<OPENAI_API_KEY> --env WORKFLOW_MCP_CONCURRENCY=<WORKFLOW_MCP_CONCURRENCY> --transport stdio standalone -- docker run -i --rm -e OPENAI_API_KEY -e WORKFLOW_MCP_CONCURRENCY docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add standalone --env OPENAI_API_KEY=<OPENAI_API_KEY> --env WORKFLOW_MCP_CONCURRENCY=<WORKFLOW_MCP_CONCURRENCY> -- docker run -i --rm -e OPENAI_API_KEY -e WORKFLOW_MCP_CONCURRENCY docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "standalone": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "-e",
                "OPENAI_API_KEY",
                "-e",
                "WORKFLOW_MCP_CONCURRENCY",
                "docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855"
            ],
            "env": {
                "OPENAI_API_KEY": "<OPENAI_API_KEY>",
                "WORKFLOW_MCP_CONCURRENCY": "<WORKFLOW_MCP_CONCURRENCY>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "standalone": {
            "type": "stdio",
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "-e",
                "OPENAI_API_KEY",
                "-e",
                "WORKFLOW_MCP_CONCURRENCY",
                "docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855"
            ],
            "env": {
                "OPENAI_API_KEY": "<OPENAI_API_KEY>",
                "WORKFLOW_MCP_CONCURRENCY": "<WORKFLOW_MCP_CONCURRENCY>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e OPENAI_API_KEY=<OPENAI_API_KEY> -e WORKFLOW_MCP_CONCURRENCY=<WORKFLOW_MCP_CONCURRENCY> standalone docker run -i --rm -e OPENAI_API_KEY -e WORKFLOW_MCP_CONCURRENCY docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855
```
Replace <…> with your own values

## When to use it
- run JavaScript workflows through Codex
- send an agent a workflow task over MCP
- execute a workflow inside Docker
- set workflow concurrency through an environment variable

## Example prompts
- Run the JavaScript workflow on these inputs.
- Execute this workflow through Codex in Docker.
- Send this task to the MCP server and return the result.

## Similar
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [Oh My Posh Validator](https://affpapa.org/en/nevibecode/mcp/oh-my-posh-validator.md) — MCP server · ★ 23654
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18779
- [Coder](https://affpapa.org/en/nevibecode/mcp/coder.md) — MCP server · ★ 17191
- [mcp](https://affpapa.org/en/nevibecode/mcp/kubeshark-mcp.md) — MCP server · ★ 12110

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md