WorkFlow Companion runs on your own machine — the client starts it, so there is no endpoint to ping. 641 installs a week from npm. Last commit 23 Oct 2026.
Claude on Windows or Linux works in your WorkFlow tasks, notes and projects via your own iCloud.
What the code does
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
try { files = fs.readdirSync(COMPANION.home).filter(f => /^pending-\d+\.json$/.test(f)); } catch (_) {}
try { spawn(cmd, args, { stdio: "ignore", detached: true }).on("error", () => {}).unref(); } catch (_) { /* the URL is printed anyway */ }
try { spawn(cmd, args, { stdio: "ignore", detached: true }).on("error", () => {}).unref(); } catch (_) { /* the URL is printed anyway */ }
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
"[Windows.UI.Notifications.ToastNotificationManager]::CreateToastNotifier('{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\\WindowsPowerShell\\v1.0\\powershell.exe').Show([Windows.UI.Notifications.ToastNotification]::new($t))";
try { spawn(cmd, args, { stdio: "ignore", detached: true }).on("error", () => {}).unref(); } catch (_) { /* the URL is printed anyway */ }
try { files = fs.readdirSync(COMPANION.home).filter(f => /^pending-\d+\.json$/.test(f)); } catch (_) {}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch WorkFlow Companion and you get told the day something new turns up.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add workflow-companion -- npx -y @opticell/workflow-companion{
"mcpServers": {
"workflow-companion": {
"command": "npx",
"args": [
"-y",
"@opticell/workflow-companion"
]
}
}
}[mcp_servers.workflow-companion]
command = "npx"
args = ["-y", "@opticell/workflow-companion"]{
"mcpServers": {
"workflow-companion": {
"command": "npx",
"args": [
"-y",
"@opticell/workflow-companion"
]
}
}
}{
"servers": {
"workflow-companion": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@opticell/workflow-companion"
]
}
}
}Alternatives to WorkFlow Companion
same job, measured the same wayManage tasks, lists, checklists, comments, and project workflows
Documents, projects, comments, workflows and data sources of your CollHub instance, as tools.
Manage projects, tasks, and workflows with Wrike project management.
Manage tasks, projects, portfolios, and team workflows
Build, validate and deploy workflows as Cloudflare Workers in your own account, with approval.
AI-powered Attio CRM access. Manage contacts, companies, deals, tasks, notes and workflows.
Local-first MCP server for Claude/Codex project wiki and graph workflows
Automate FinOps workflows, cases, and cloud ops via the Wiv Workflow API.
WorkFlow Companion — questions
Answers built from our own checks of this server.