WorkFlow Companion
NPM · @OPTICELL/WORKFLOW-COMPANION · 2 COMPONENTS
Claude on Windows or Linux works in your WorkFlow tasks, notes and projects via your own iCloud.
Available components
Last scanned (9 hours ago)
Scores higher than 36% of npm servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2031 tokens (~70/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "workflow_remove_subtasks" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +23
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Tool coverage: 33 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- 12 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/@opticell/workflow-companion@1.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
workflow_add_document_version ~64
Upload a new version of a document. The current file is kept in its history; the profile and folder carry over.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | What changed |
| document | string | yes | – |
| file | string | yes | Path to the file on this computer |
No output schema declared.
No examples provided.
workflow_add_subtasks ~35
Add subtasks to an existing task's checklist.
| Name | Type | Req | Description |
|---|---|---|---|
| subtasks | array | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
workflow_attach_file ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the file on this computer |
| name | string | – | Display name; defaults to the filename |
| task | string | yes | – |
No output schema declared.
No examples provided.
workflow_check_subtasks ~60
Tick subtasks off a task (or untick them), so progress on a long job is visible on the task's own row.
| Name | Type | Req | Description |
|---|---|---|---|
| subtasks | array | yes | – |
| task | string | yes | – |
| uncheck | boolean | – | – |
No output schema declared.
No examples provided.
workflow_comment ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mentions | array | – | – |
| task | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
workflow_complete_task ~21
Mark a task complete.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
No output schema declared.
No examples provided.
workflow_convert_note ~87
Promote a note into a task, keeping the note and linking the two. Converting is what takes a note out of the inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | – |
| due | string | – | – |
| note | string | yes | – |
| priority | string | – | – |
| project | string | – | – |
| subtasks | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
workflow_create_note ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| color | string | – | #RRGGBB |
| pin | boolean | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
workflow_create_project ~104
Create a project, or update an existing one of the same name.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | #RRGGBB |
| description | string | – | – |
| icon | string | – | SF Symbol name |
| name | string | yes | – |
| start | string | – | planned start yyyy-MM-dd, or 'none' to clear |
| status | string | – | – |
| target | string | – | target date yyyy-MM-dd, or 'none' to clear |
No output schema declared.
No examples provided.
workflow_create_task ~136
Create a task. Set assignee to "Companion" to put it in your own queue.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | – |
| comment | string | – | An opening comment on the new task |
| due | string | – | ISO-8601 or yyyy-MM-dd |
| notes | string | – | – |
| priority | string | – | – |
| project | string | – | – |
| status | string | – | To Do / In Progress / Completed |
| status_note | string | – | Seeds the pinned status line |
| subtasks | array | – | – |
| tags | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
workflow_draft_email ~106
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 the user has set Settings → Agent Bridge → Email to Draft Only or Can Send.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | plain text |
| cc | array | – | – |
| subject | string | yes | – |
| task | string | yes | – |
| to | array | yes | bare addresses, no display names |
No output schema declared.
No examples provided.
workflow_file_document ~94
File a local file straight into a project's workspace (not onto a task), with an optional profile and folder.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| description | string | – | – |
| file | string | yes | Path to the file on this computer |
| folder | string | – | – |
| name | string | – | – |
| project | string | yes | – |
| status | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
workflow_get_document ~45
One document in full: profile, folder, every version with its comment, and the start of its text.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | WF-number, id or file name |
No output schema declared.
No examples provided.
workflow_get_note ~21
One note in full.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
No output schema declared.
No examples provided.
workflow_get_task ~40
One task in full, with its checklist and comment thread. Accepts a task id or a fragment of its title.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
No output schema declared.
No examples provided.
workflow_list_documents ~97
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 and the text inside PDFs, scans and text files.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | default 40 |
| project | string | – | – |
| query | string | – | – |
| status | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
workflow_list_notes ~37
The Notepad. A '*' marks notes addressed to you (containing @Companion).
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include archived notes |
No output schema declared.
No examples provided.
workflow_list_projects ~61
The portfolio: every project's status, planned dates, progress and health (overdue / atRisk / idle / onTrack / planning / onHold / done) with the reason, as the Projects tab shows it.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | include archived |
No output schema declared.
No examples provided.
workflow_list_tasks ~33
List tasks with status, priority, project and due date.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include hidden and completed tasks |
No output schema declared.
No examples provided.
workflow_ping ~22
Confirm the app is watching the bridge (round-trips one command).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
workflow_poll_comments ~41
Comments the user has written recently, ignoring the agent's own. Defaults to the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | ISO-8601 |
No output schema declared.
No examples provided.
workflow_queue ~69
Your inbox as "Companion": tasks assigned to Companion, tasks whose recent comments say @Companion, and notes that say @Companion — each with why it's here, its status line, checklist and latest comment. Work meant for another agent (such as Claude on the Mac) is not yours.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
workflow_remove_subtasks ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| subtasks | array | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
workflow_rename_subtask ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | current title, exact or a fragment it contains |
| task | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
workflow_reply_note ~74
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 note gets an answer on the user's phone.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| pin | boolean | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
workflow_set_status_line ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
workflow_state ~32
Whether the Agent Bridge is running, where it lives, and the app version. Use this first if anything else fails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
workflow_update_document ~139
Change a document's profile or folder. Profile fields apply to every version; 'name' renames the current file. Folders nest with '/', and '' unfiles.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| description | string | – | – |
| document | string | yes | – |
| folder | string | – | – |
| name | string | – | – |
| status | string | – | Draft, In Review, Final, Signed, Superseded |
| type | string | – | Contract, Agreement, Invoice, Quote, Receipt, Letter, Email, Report, Proposal, Minutes, Specification, Drawing, Photo, Form, Policy, Other — or your own |
No output schema declared.
No examples provided.
workflow_update_task ~217
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 formatting. 'add_tags'/'remove_tags' edit tags one at a time without dropping ones the user added.
| Name | Type | Req | Description |
|---|---|---|---|
| add_tags | array | – | – |
| append_notes | string | – | added to the end of the notes |
| assignee | string | – | empty string unassigns |
| due | string | – | ISO-8601 or yyyy-MM-dd |
| in_my_day | boolean | – | – |
| no_due_date | boolean | – | true removes the due date |
| notes | string | – | replaces the notes; empty string clears them |
| priority | string | – | – |
| project | string | – | empty string removes it from its project |
| remove_tags | array | – | – |
| status | string | – | To Do / In Progress / Completed |
| task | string | yes | id or title |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the WorkFlow Companion MCP server?
WorkFlow Companion runs locally as an npm package, launched with npx -y @opticell/workflow-companion. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @opticell/workflow-companion
claude mcp add teamdzx-workflow-companion -- npx -y @opticell/workflow-companion
What is the WorkFlow Companion MCP server?
WorkFlow Companion is an MCP server listed in the public MCP registry as io.github.TeamDzX/workflow-companion. Claude on Windows or Linux works in your WorkFlow tasks, notes and projects via your own iCloud. This page covers its npm package (@opticell/workflow-companion).
Is the WorkFlow Companion MCP server safe to use?
WorkFlow Companion scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WorkFlow Companion MCP server expose?
WorkFlow Companion exposes 29 tools: workflow_state, workflow_list_tasks, workflow_get_task, workflow_queue, workflow_poll_comments, and 24 more. Their descriptions and schemas cost roughly 2,031 tokens of context every time the server is loaded.
Is the WorkFlow Companion MCP server still maintained?
WorkFlow Companion is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the WorkFlow Companion MCP server under?
WorkFlow Companion declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.