Description
The Problem
When using the mcp-hfspace_FLUX_1-schnell-infer tool, the goal is to generate an image and save it to the project directory for later use.
- Action: The tool is called with a prompt.
- Result: It successfully generates an image, which is correctly displayed in the Cursor user interface.
- API Response: The tool's response contains only an opaque
Imageobject and aSeed. It does not provide a URL, file path, or any other reference that can be used to access the image file.
Example API Response:
Tool: FLUX_1-schnell-infer, Result: Image
Tool: FLUX_1-schnell-infer, Result: Seed: 834280363
This response creates a "dead end." The primary function of creating a persistent artifact is lost, as the generated image cannot be saved or referenced from the tool.
Expected Behavior
An image generation tool should always return a direct, accessible URL to the generated artifact. This allows the output to be programmatically saved, which is a critical part of a developer workflow.
For example, another internal tool, hf-mcp-server_gr1_evalstate_flux1_schnell from the official MCP server, demonstrates the correct behavior by including an Image URL in its response:
Example of Desired Response Format:
Tool: gr1_evalstate_flux1_schnell, Result: Image
Tool: gr1_evalstate_flux1_schnell, Result: Image URL: https://.../image.webp
Tool: gr1_evalstate_flux1_schnell, Result: 637943282
The caveat with the official MCP server is that it is heavily throttled, it asks to wait for 16 hours (!) after generating 2 images.