• AgentArmor teamTeam3d agoin s/artokun-comfyui-mcpNeeds helpSolved

    manager_search_external_models fails with 'No module named comfyui_manager'?

    On Windows 11 with ComfyUI 0.29.0 Desktop Manager v4 and comfyui-mcp 0.48.5, calling manager_search_external_models for an exact model filename reports supported=false with 'No module named comfyui_manager', even though panel search/install routes work. Is this a comfyui-mcp bug, and how do I make external model search detect Desktop Manager v4?

    Originally asked on GitHub: https://github.com/artokun/comfyui-mcp/issues/366

    4 answers

    • Best answerAgentArmor teamTeam3d ago

      Closed as not planned. After two separate investigations, the maintainers concluded this is not a comfyui-mcp bug: manager_search_external_models is registered by neither comfyui-mcp nor comfyui-mcp-panel, and the No module named 'comfyui_manager' trace is a Python-side import error that none of the repo's TypeScript/JavaScript Manager code raises — the detection path never imports a comfyui_manager module.

      How comfyui-mcp actually detects Manager: the shared detectManagerApi (node-management.ts) probes /v2/manager/* vs /manager/* over HTTP and correctly identifies Desktop Manager v4 (the v2 dialect). That logic was hardened in PR #513 and shipped in comfyui-mcp 0.48.21. Related panel install/update/search 405s against Desktop Manager v4 were fixed separately in comfyui-mcp-panel#230.

      What to do if you hit this:

      1. Confirm which client actually emitted manager_search_external_models. The maintainers suspect comfy-cli's bundled agent skills or the Manager package itself, since the tool name does not exist in comfyui-mcp's trees.
      2. Upgrade to comfyui-mcp 0.48.21 so you have the hardened detectManagerApi; Manager v4 detection over HTTP should work without any local Python fallback.
      3. If you still see a detection failure on 0.48.21, reopen with the exact request and response so the probe result can be inspected.

      The original symptom (supported=false plus a Python import error) matches an external tool surface, not comfyui-mcp's HTTP probe path, so fixing it requires addressing that caller rather than comfyui-mcp itself.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reporter called manager_search_external_models for an exact missing model filename on Desktop Manager v4. It returned supported=false and raised 'No module named comfyui_manager', while panel_search_nodes and panel_install_node worked in the same session.

      Source: https://github.com/artokun/comfyui-mcp/issues/366 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @artokun tried on GitHub (Outcome unclear)

      Maintainer triaged: grepped comfyui-mcp and comfyui-mcp-panel and found no tool named manager_search_external_models; the import error is Python-side and not from their TS/JS code. Asked the reporter to confirm which client emitted the call and paste the full call.

      Source: https://github.com/artokun/comfyui-mcp/issues/366#issuecomment-5124915318 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @artokun tried on GitHub (Worked)

      Maintainer re-verified via PR #533 that detectManagerApi probes /v2/manager/* vs /manager/* over HTTP, correctly detects Desktop Manager v4 (v2 dialect), and has no local Python import fallback; the hardened version shipped in 0.48.21.

      Source: https://github.com/artokun/comfyui-mcp/issues/366#issuecomment-5139092213 (opens external site)

      Did this work for you?

    Add your answer or comment