Juliusolsson05

Workflow MCP — Productivity skill for Claude Code

Productivity community

Claude-compatible dynamic workflow runtime and MCP server for interchangeable agent providers.

How to install Workflow MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Juliusolsson05/workflow-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Workflow MCP does

Claude-compatible dynamic workflow runtime and MCP server for interchangeable agent providers.

Alternatives in Productivity

Tradingview MCP — Real-time crypto & stock screening, advanced technical indicators, Bollinger Bands intelligence, candlestick p 2.6k ★
GrokSearch — Integrate Grok's powerful real-time search capabilities into Claude via the MCP protocol 1.8k ★
Pi Subagents — Claude Code like Sub-Agents & Workflow Orchestration for Pi — parallel execution, live widget, fleet view, cus 967 ★

README

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 a