Developer · Local MCP server
Workflow MCP
Session-bound Docker workflow server through Codex. State is discarded with the container.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Juliusolsson05/workflow-mcp- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-07-27
- Updated
- 2026-07-27
- Publisher
- Juliusolsson05 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Juliusolsson05) · how
- Listed under
- Docker MCP servers
- Website
- github.com/Juliusolsson05/workflow-mcp/tree/main/standalone
- Repository
- github.com/Juliusolsson05/workflow-mcp (folder standalone)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855 | - | stdio |
How to connect Workflow MCP
Workflow MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e OPENAI_API_KEY -e WORKFLOW_MCP_CONCURRENCY docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855. It reads these environment variables: OPENAI_API_KEY (required, secret) and WORKFLOW_MCP_CONCURRENCY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"workflow-mcp": {
"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": "<secret>",
"WORKFLOW_MCP_CONCURRENCY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Word MCP Server (FsWordDsl)Word tools for AI agents: read/write, decompile to F#/C#/XML/JSON, or build from XML/JSON. | Local · stdio |
| Wordpress Privacy LintFinds the 12 author-side privacy duties your plugin PHP breaks, with the article and the fix on ever. | Local · stdio |
| WorkfileRepository-native protocol and local MCP server for Work, Docs, History and durable project Memory. | Local · stdio |
| Workflow GeneratorArchitecture diagram with concurrency capacity and bottleneck estimates from any codebase. | Local · stdio |
| Workflows MCP ServerStore, query, and create YAML workflow playbooks for LLM agents. | Local · stdio, HTTP |
| WorkflowyCreate, update, complete nodes, search & replace with regex and dry run, usage reports, transforms. | Local · stdio |
| WorkingMemoryPersistent personal memory for AI assistants - save, search, and recall across every MCP client. | Remote · HTTPLive check: ✓ handshake |
| WORKMINEX402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers. | Remote · HTTPLive check: ✓ handshake |