I’ve been using MCP integration between workflowy and claude desktop. This stopped working a few days ago, and I managed to get the following diagnostic info out of claude desktop. Does anyone recognize this issue? Thanks
The read executed and serialised correctly.
The bug is where it puts that payload:
"result":
{
"content": [{"type":"text","text":"success"}], ← what clients read
"structuredContent": {"results": ["...your outline..."]} ← where the data actually is
}
Workflowy returns the tree in structuredContent only, and puts the literal string "success" in the content[] array. Claude Desktop — like most MCP clients — surfaces content[]. So every read I ran returned exactly what the server told it to: the word success.
That is a spec violation on Workflowy’s part. The MCP specification requires that tools returning structuredContent also provide the serialised JSON in a text content block, precisely for backwards compatibility with clients that read content[]. They’ve returned a status string instead of the data.