Has Workflowy Not Properly Implemented the MCP for Use in Claude?

This topic was automatically generated from Slack. You can find the original thread here.

It seems that although I connected the Workflowy MCP, it actually cannot be used in Claude. I configured several others—Toggl, Microsoft To Do, and Raindrop—and they all work, but only Workflowy does not. Does this mean Workflowy hasn’t actually implemented it properly yet?

To explain a bit, an app integration can be seen in two parts: an auth piece, and a piece composed of different components and actions. When the auth piece is ready, we publish it in Pipedream app store. This is the entry for Workflowy Pipedream If you scroll down that page you’ll see there are no triggers nor actions as of writing (compare vs Pipedream which has several). The actions of an app integration are surfaced in as tools in Pipedream MCP.

Would you mind requesting specific actions you require in Workflowy? You can follow this link Sign in to GitHub · GitHub and use the first template “Action Request”. You use follow this Affinity issue as an example for specifying actions in your request

Please add the following actions for the Workflowy integration:
1. Create Node — Create a new node/bullet, with options to set its name, note, and parent node.
2. Search Nodes — Search nodes by keyword, returning matching nodes with their IDs and content.
3. Update Node — Update an existing node’s name or note by node ID.
These are the most essential actions for using Workflowy programmatically. Thank you!

Happy to help with that . Feel free to subscribe to updates [ACTION] WorkFlowy new actions · Issue #20230 · PipedreamHQ/pipedream · GitHub Thanks!