comfyui-mcp get_node_info: "No nodes found" for a node present in /object_info
In comfyui-mcp 0.48.6 on Windows 11 with ComfyUI 0.29.0, get_node_info(node_type="DetectorForNSFW") returns "No nodes found matching "DetectorForNSFW"" even though the live /object_info response includes that exact node. This happened after installing comfyui-utils-nodes 1.4.2 and restarting. Why does the lookup miss it, and what's the fix?
Originally asked on GitHub: https://github.com/artokun/comfyui-mcp/issues/404
4 answers
Fixed in comfyui-mcp 0.48.8. Per the maintainer, get_node_info now honors the live /object_info registration key (#432). Update with
npm i -g comfyui-mcp@latest, then call get_node_info again for the same node type; if it still fails, reopen the issue with the version you are on.The thread does not confirm the underlying cause beyond the stale-lookup observation. The maintainer only suggested retitling the issue to "invalidate node-info cache after custom-node installation/restart". The reporter proposed refreshing from the live /object_info endpoint or invalidating the node-info cache after custom-node installation, but marked it as not applied locally ("applied locally: no"), so that is not a verified workaround. No exact cache-invalidation command is given in the thread, so if you cannot upgrade, check the tool's own docs before guessing (general advice).
Did this work for you?What @artokun tried on GitHub (Outcome unclear)
Maintainer fixed the issue in comfyui-mcp 0.48.8 so get_node_info uses the live /object_info registration key, and instructed updating with
npm i -g comfyui-mcp@latestand reopening if it persisted.Source: https://github.com/artokun/comfyui-mcp/issues/404#issuecomment-5126991700 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter installed comfyui-utils-nodes 1.4.2, restarted, verified DetectorForNSFW is in /object_info, then called get_node_info and got "No nodes found matching "DetectorForNSFW"".
Source: https://github.com/artokun/comfyui-mcp/issues/404 (opens external site)
Did this work for you?What @artokun tried on GitHub (Outcome unclear)
Owner suggested renaming the issue to "invalidate node-info cache after custom-node installation/restart".
Source: https://github.com/artokun/comfyui-mcp/issues/404#issuecomment-5124881848 (opens external site)
Did this work for you?
Related questions
- Use comfyui-mcp with Hermes Agent or Openclaw instead of Claude Code?
- ComfyUI-MCP apply_manifest clones duplicate ComfyUI-Manager from Krea 2 pack
- ComfyUI MCP Codex callback commits render as [object Object] instead of streamed text
- comfy_cli_models errors "comfy-cli was not found" even with a connected ComfyUI workspace
- comfyui-mcp: panel_get_errors stale after panel_set_widget fixes missing model?