WorkFlow Companion

Name: WorkFlow Companion
Author: TeamDzX

作者：TeamDzX版本 2.6.0i★ –i在你的电脑上运行

注册名称io.github.TeamDzX/workflow-companion

安装

概览

作者提供的说明（英文原文）

Claude on Windows or Linux works in your WorkFlow tasks, notes and projects via your own iCloud.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

claude mcp add workflow-companion -- npx -y @opticell/workflow-companion

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "workflow-companion": {
      "command": "npx",
      "args": [
        "-y",
        "@opticell/workflow-companion"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "workflow-companion": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@opticell/workflow-companion"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 TeamDzX 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 3531 个服务器的 0%
发布到注册中心的时间比此分类中其他 3531 个服务器的 99% 更新
基础检查结果等于或优于此分类中其他 3531 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

WorkFlow Companion 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.6.0）于今天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, MCPB。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT7天前更新

安装

MCP Server for Excel

作者：sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT4天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

WorkFlow Companion

This repository is WorkFlow Companion's home: the source (src/index.js,

MIT licensed), downloads (WorkFlow.mcpb for Claude Desktop) on the

Releases page,

and bugs and requests in Issues.

The package itself installs from npm. On a Mac, use the open-source

workflow-agent-bridge instead.

All of Opticell's free tools for Claude: opticell-mcp.

Lets Claude on Windows or Linux work in your WorkFlow tasks, notes and projects: reading the queue, replying in threads, ticking checklists, filing notes, updating documents. It works in Claude Code, Claude Desktop, or any MCP client.

Free. It needs WorkFlow 5.2 or later on an iPhone, iPad or Mac, which does the actual work. No Mac needed:

Claude ──MCP──▶ companion ──▶ your private iCloud ──▶ WorkFlow on your iPhone, iPad or Mac

◀── receipt + fresh snapshot

The companion never edits your WorkFlow data itself. It leaves commands in a zone of your own private iCloud database. WorkFlow applies them with the same checks as the app (read-only trial gate, email permission, the agent's signature) and lists every one in Command History. Nothing passes through Opticell's servers.

Which device answers. A Mac with WorkFlow open answers within seconds. An iPhone or iPad answers when iOS lets WorkFlow run: usually within minutes, sometimes only when you next open it, and not while WorkFlow has been swiped away in the app switcher. With both switched on, the Mac answers while it's awake and the iPhone stands by. Every command is applied exactly once, however many devices are on.

Install

One line installs Node.js if needed, signs this computer in, adds the companion to Claude Code and offers to let it start work on its own:

Windows (PowerShell):

irm https://raw.githubusercontent.com/TeamDzX/workflow-companion/main/install.ps1 | iex

Mac or Linux (Terminal):

curl -fsSL https://raw.githubusercontent.com/TeamDzX/workflow-companion/main/install.sh | sh

Switch the companion on in WorkFlow first (step 1 below). The steps that follow are what the installer does, if you'd rather do them by hand.

Set up

In WorkFlow on an iPhone or iPad: Settings → Windows Companion → Answer the Companion. On a Mac: Settings → Agent Bridge, then the Agent Bridge and Cloud Bridge switches.
Install Node.js 18 or later (LTS) if node -v doesn't show it: Windows winget install OpenJS.NodeJS.LTS -e, Mac brew install node, Linux your package manager, or the installer from https://nodejs.org. Then close and reopen the terminal (and restart Claude Code) so node and npx are found; otherwise you'll see "node is not recognized".
In a normal terminal window:

   npx -y @opticell/workflow-companion@latest setup

It opens https://companion.opticell-limited.com to sign in with the Apple Account WorkFlow uses on your iPhone or Mac, then asks you to paste the token that page shows. It asks questions, so it can't run from Claude Code's ! prompt or another non-interactive shell; there, pass --web-token and --name .

Add it to Claude:

   claude mcp add --scope user workflow -- npx -y @opticell/workflow-companion@latest

On Windows, npx is a script, so Claude Code needs cmd /c in front:

   claude mcp add --scope user workflow -- cmd /c npx -y @opticell/workflow-companion@latest

--scope user makes it available in every project on this computer.

Claude Desktop needs no terminal. Download WorkFlow.mcpb from the product page and double-click it. Then sign in at https://companion.opticell-limited.com and paste the token into Settings → Extensions → WorkFlow Companion → Sign-in token.

Check it any time with npx -y @opticell/workflow-companion status.

Its name

Setup asks what Claude on this computer should be called in WorkFlow ("Companion" unless you choose, e.g. --name Server). That name is how work reaches it rather than the Mac's own Claude:

Assign a task to it. WorkFlow offers the name once it has heard from the companion, and the Ask sheet lets you pick it.
Write `@Server` in a comment or a note. A mention in a *shared* project's thread doesn't count, because other people can write there.
What it writes is signed with its name, so a thread shows which Claude did what.
One name, one computer. Setup refuses a name another computer already answers to, and asks for another. Every command is checked the same way, which covers Claude Desktop, where the name is a setting. Use setup --takeover when this computer replaces the other one. A name frees up by itself once its computer has been silent for two weeks.
@Claude always means Claude on the Mac. A companion can't take that name, and mentions match whole words only, so @Claude2 never wakes the Mac.

Claude Desktop users set the name in the extension's settings.

Working on its own

With waking on, @Server from the app is enough: nobody has to be at this computer. Turn it on once Claude Code is installed and signed in here:

npx -y @opticell/workflow-companion wake-on

Every 2 minutes a hidden scheduled job (Task Scheduler on Windows, cron elsewhere) checks this name's queue in iCloud. That's one small call; the task list is downloaded only when it changed.
New work starts one Claude Code session (claude -p, no window). It reads the task, comments that it's picked it up (your phone shows "Server is on it"), does the work and replies in the thread.
What counts as new: a task newly assigned to the name, a new @Server comment from a person, a person's follow-up on an assigned task, or an edited note that mentions it. Its own replies never wake it.
Handled once. One session at a time; work already handled never starts another. A session that couldn't start at all (not signed in to Claude, a usage limit) is retried twice more, then says so in the thread.
A time limit, 45 minutes by default (--max-minutes). A session stopped by it says so in the thread.
What it may do. By default the WorkFlow tools (mcp__workflow), for reading tasks and replying, plus WebSearch and WebFetch, so it can research what you ask. Web pages it reads could try to mislead it, and a URL it fetches can carry text out; --no-web turns web access off, --web back on. Scheduled briefs, check-ins and the self-test never get it. To let it run commands on this computer, pass --allow-tools "mcp__workflow Bash Read" (any Claude Code permission rules). Anyone who can write @Server in your WorkFlow could then run commands here, so decide that deliberately. Shared projects never reach it.
Windows: a scheduled task normally runs only while the user is logged in. To run while logged off, change the task "WorkFlow Companion wake" to "Run whether user is logged on or not" in Task Scheduler.
--workdir sets the folder sessions start in (your home folder otherwise), --model the Claude model, --claude the path to Claude Code if it isn't found. --skip-existing treats what's already queued as handled.
The log is ~/.workflow-companion/wake.log. wake-off stops it all.

Staying up to date

Claude Code runs whatever its registration names. Register it with @latest (setup prints the exact line) and every new session uses the newest release.
The scheduled jobs (keep-alive, waking) run a saved copy that npm never touches, so they update themselves. At most every 6 hours they read npm's entry for the package (registry.npmjs.org/@opticell/workflow-companion/latest). When it's newer, they download the release, check it against npm's sha512 checksum and that Node can parse it, then swap it in. Turn this off with auto-update off, and update by hand with update.
Its version is reported. Every ten minutes or so while it runs, each companion writes its version, computer and check-in time to your iCloud. WorkFlow 5.3.2 shows them in Settings → Agent Bridge → Who's Bridged, and status lists every companion's version.

Commands


`workflow-companion`	Runs the MCP server. This is what Claude starts.
`workflow-companion setup`	Signs this computer in. Takes `--web-token` to skip the prompt.
`workflow-companion status`	Which device answers, how fresh the snapshot is, any receipts that arrived late.
`workflow-companion doctor`	Checks everything on this computer and says how to fix what's wrong. Start here when something isn't working.
`workflow-companion canary`	Runs the daily self-test now. `canary on\	off`,` canary at HH:MM`.
`workflow-companion keepalive`	Renews the sign-in. The scheduled job runs this.
`workflow-companion update`	Updates the scheduled jobs' copy to the latest release now, and shows how to keep Claude Code on `@latest`.
`workflow-companion auto-update on\	off`	Whether the scheduled jobs update themselves (on by default).
`workflow-companion wake-on`	Starts a Claude Code session on its own when work for its name arrives. See above.
`workflow-companion wake-off`	Stops that. Work waits until you ask Claude here.
`workflow-companion wake`	One check of the queue. The scheduled job runs this.
`workflow-companion monitor add\	list\	check\	remove`	Checks this computer runs without using Claude. See below.
`workflow-companion approvals on\	off`	Lets an assistant run one exact command after you reply "approve CODE" (off by default).
`workflow-companion inbox-on\	inbox-off`	Files dropped in a folder become tasks.
`workflow-companion notifications on\	off`	Notices on this computer (on by default). `notify-test` shows one.
`workflow-companion reports on\	off`	A short report attached to the task after each session (on by default).
`workflow-companion signout`	Deletes the sign-in, cached data and both scheduled jobs.

On this computer, by itself (1.8)

These run in the same 2-minute scheduled job as waking, and cost no Claude usage.

Monitors. Checks that wake Claude only when something changes:

workflow-companion monitor add --name site --http https://example.com --task "Server status" --wake

workflow-companion monitor add --name disk --disk C:\ --min-gb 20 --task "Server status" workflow-companion monitor add --name api --port 10.0.0.5:443 --every 2 workflow-companion monitor add --name backup --file D:\backups\latest.zip --task "Backups" workflow-companion monitor add --name nightly --command "check-backups.cmd" --task "Backups" --wake

A change (down, back up, the file changed) is posted on the task, shows a notification here, and with --wake starts a session about it. An assistant can set up website, port, disk, process and file monitors itself (workflow_monitor), but only you can add a command monitor, because it runs a command every few minutes.

Approvals. An assistant can ask to run one exact command on this computer (restart a service, install an update). It posts the command on the task with a code; reply approve K7Q2 (or decline K7Q2) from your phone. Only a person's reply counts, never another assistant's; tasks in shared projects ca

只显示了开头部分；其余内容请在仓库中阅读

WorkFlow Companion

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“文档、表格与办公”中的其他服务器比较i

常见问题

替代选择

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

作者的 README

WorkFlow Companion

Install

Set up

Its name

Working on its own

Staying up to date

Commands

On this computer, by itself (1.8)