Hi Rodolfo
Following on from my first report, Claude wanted to add something:
I use the MCP server built into the WorkFlowy Beta desktop app on macOS, currently 4.3.2608051824-beta, and it has become the main way I work with my account. It is fast, it resolves mirrors, and nothing has to leave my machine. It is genuinely very good.
There is one gap, and it is a big one for me: the note — the grey text under a bullet — is not exposed at all. I cannot read a note, write one, edit one, or clear one through any of the local tools.
I checked this by asking the running server for its own tool list rather than going by documentation. It offers seven tools: tree_seek, tree_zoom, tree_patch, message_success, attachments_pull, attachments_attach and screencap_capture. None of them has a note parameter.
Concretely:
- tree_patch is the only tool that changes anything, and its full set of operations is replace (bullet text only), complete, uncomplete, insert_after, insert_before, move and delete. There is no note field on any of them, including the two insert operations, so I cannot even create a bullet with a note already attached.
- tree_seek leaves notes out of its results entirely. Reading a bullet whose note says “KANBAN” gives me the bullet text and nothing more. I could not find a flag to include notes.
Why this matters: notes are where the actual information lives for a lot of us. Every task in my account carries info like due date, effort estimate, blocking dependency and owner in its note. So the local server can do everything to a bullet except touch the part that holds its data, and anything that maintains that data has to fall back to the cloud API — which means depending on a network connection, sending data off the machine, and maintaining two connections instead of one. That undoes much of the reason to have a local server.
What I would like:
- Notes included in tree_seek results, ideally behind an optional flag so existing callers do not suddenly get much larger responses.
- A note parameter on tree_patch — on insert_after and insert_before so a bullet can be created complete, and either on replace or as its own replace-note operation.
- A way to clear a note back to genuinely empty and deleted.
On that third point, in case it is useful to whoever picks this up: clearing a note appears to be impossible through the public API too, not just locally. Sending empty text returns “specify at least one of name, note, or layout_mode”, which I assume is a guard against empty requests but which also blocks clearing on purpose. A single space is rejected the same way through MCP. It works through the command-line tool only if the space is passed as a separate argument — --note " " succeeds while --note=" " fails — and the bullet then holds a note containing one space, which looks blank but is not.
One small documentation point while I am here. The command-line tool describes --note as “Additional note content”, which reads as though it appends to an existing note. It does not — it replaces the note completely. I lost a note finding that out. Wording it as a replacement would save someone else the same.
Happy to give more detail on any of this if it is helpful. Thanks for the local server — the note field is the only thing standing between it and being all I need.
Mock node (MCP curl test) was created at the top level, right after ♖ DashBoard. Check your Workflowy to confirm.