# @opticell/workflow-companion Lets Claude on Windows or Linux work in your WorkFlow tasks, notes and projects, through WorkFlow for Mac and your own iCloud. An MCP server. - **Type:** MCP server - **Trust:** 85/100 (A), scored on the package rubric - **Verification:** verified (build provenance) - **Version:** 1.9.0 - **Author:** Opticell Limited - **License:** MIT - **npm:** @opticell/workflow-companion - **Source:** https://github.com/TeamDzX/workflow-companion - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 85/100 (A), scored on the package rubric - Publisher verified: no - Build provenance: verified attestation - npm trusted publishing (OIDC): yes - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-10-21T22:17:53.464Z - **Version scanned:** 2.0.0 - **CVEs:** none found by OSV at scan time ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `workflow_state` — Whether the Agent Bridge is running, where it lives, and the app version. Use this first if anything else fails. - `workflow_list_tasks` — List tasks with status, priority, project and due date. - `workflow_get_task` — One task in full, with its checklist and comment thread. Accepts a task id or a fragment of its title. - `workflow_queue` - `workflow_poll_comments` — Comments the user has written recently, ignoring the agent's own. Defaults to the last 24 hours. - `workflow_create_task` - `workflow_comment` — Post a comment on a task, authored as the agent. This is how you reply to the user — it reaches their phone as a notification. - `workflow_set_status_line` — Set a task's pinned note — the one-line 'where this stands' shown above its comments. Overwrite it as work progresses rather than commenting each time. - `workflow_check_subtasks` — Tick subtasks off a task (or untick them), so progress on a long job is visible on the task's own row. - `workflow_add_subtasks` — Add subtasks to an existing task's checklist. - `workflow_update_task` — Change an existing task. Only the fields you pass are touched. 'notes' REPLACES the notes; prefer 'append_notes', which adds to the end and keeps the user's for - `workflow_remove_subtasks` — Delete rows from a task's checklist. Each entry must be an exact title or a fragment only one row contains; anything ambiguous is left alone. - `workflow_draft_email` — Prepare an email a task asks for. It is attached to the task as a draft the user checks and sends with Review & Send; nothing is sent from here. Refused unless - `workflow_rename_subtask` — Retitle one subtask in place, keeping its tick state — for correcting a row's wording (a version line on an index, say) without adding a duplicate. - `workflow_complete_task` — Mark a task complete. - `workflow_create_project` — Create a project, or update an existing one of the same name. - `workflow_list_notes` - `workflow_get_note` — One note in full. - `workflow_create_note` — File a note in the Notepad. Where output that isn't work belongs — a summary, a finding, a set of options. Use a task instead for anything that needs doing. - `workflow_reply_note` — Answer a Notepad note inside the note itself: appends a signed, dated reply without changing what the user wrote. Notes have no comment thread, so this is how a - `workflow_convert_note` — Promote a note into a task, keeping the note and linking the two. Converting is what takes a note out of the inbox. - `workflow_attach_file` — Attach a local file to a task (a report, a document, an image). The file is copied into the bridge folder and consumed by the app. - `workflow_list_projects` — The portfolio: every project's status, planned dates, progress and health (overdue / atRisk / idle / onTrack / planning / onHold / done) with the reason, as the - `workflow_list_documents` — List or search documents — every file on a task, on a note, or filed in a project's workspace. The query matches names, document numbers (WF-4F2A91), profiles a - `workflow_get_document` — One document in full: profile, folder, every version with its comment, and the start of its text. - `workflow_update_document` — Change a document's profile or folder. Profile fields apply to every version; 'name' renames the current file. Folders nest with '/', and '' unfiles. - `workflow_file_document` — File a local file straight into a project's workspace (not onto a task), with an optional profile and folder. - `workflow_add_document_version` — Upload a new version of a document. The current file is kept in its history; the profile and folder carry over. - `workflow_watch` — Set a task aside and be woken to look at it again later: "tell me when the release merges, check every hour", "remind me at 15:00". Give minutes from now or a t - `workflow_hand_off` — Hand a task to another assistant (Claude, or a companion such as Jarvis) or to a person: it becomes the assignee and a comment says so, with your note. Handing - `workflow_house_rules` — The user's house rules: standing instructions for every assistant, set in WorkFlow (Settings → Agent Bridge → House Rules). Read them before starting work. Only - `workflow_monitor` — Checks that run on this computer every few minutes without using Claude, and wake you only when something changes: a website (http), a port (host:port), free di - `workflow_request_approval` — Ask the user to approve one command before it runs on this computer (restart a service, install an update, delete old backups). Posts the exact command on the t - `workflow_check_approval` — Whether the user has approved or declined an approval request (by its code). - `workflow_run_approved` — Run a command the user has approved, exactly as it was when they approved it. Once only. Returns its exit code and output; report the result in the task's threa - `workflow_doctor` — Check the companion on this computer end to end (sign-in, WorkFlow publishing and answering, version, scheduled jobs, Claude Code, last session, monitors) and s - `workflow_ping` — Confirm the app is watching the bridge (round-trips one command). - `workflow_list` — List or search. kind: tasks (default; open ones unless all), notes (the Notepad; '*' marks ones addressed to you), projects (status, dates, progress, health and - `workflow_get` — One task (with checklist and comment thread), note, or document (profile, folder, versions, start of its text) in full. Give an id, a WF-number, or a fragment o - `workflow_note` — The Notepad. action create files a note: where output that isn't work belongs (a summary, a finding, options); use a task for anything that needs doing. reply a ## Install **Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"workflow-companion\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@opticell/workflow-companion\"\n ]\n }\n }\n}" ``` ## Blast radius Extensive blast radius — deletes data; runs on your machine. - Floor 35, ceiling 59 (tier: extensive) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40opticell%2Fworkflow-companion - Install plan: https://forgeregistry.com/api/v1/packages/%40opticell%2Fworkflow-companion/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40opticell%2Fworkflow-companion - HTML page: https://forgeregistry.com/registry/%40opticell%2Fworkflow-companion - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.