Cursor can build the whole app, but it can’t make the placeholder images and concept art that go in it. Flux isn’t built into Cursor either. Add AiWings as an MCP server once, and the Cursor agent can generate Flux Fast images for a single credit each and save them straight into your project.
What you need
- Cursor with Agent mode.
- An AiWings account (sign in with Google). Usage comes from your AiWings credits.
- About a minute.
Step 1: Add AiWings to Cursor
The fastest way is the one-click Add to Cursor button on the AiWings Cursor page. To set it up by hand, follow these steps.
- 1Add the config below to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this project only).
- 2Open Cursor Settings → MCP and click Connect next to AiWings.
- 3Sign in to AiWings in the browser window and allow access.
- 4Check that AiWings shows a green dot and its tools are listed.
{
"mcpServers": {
"aiwings": { "url": "https://aiwings.io/api/mcp" }
}
}Step 2: Ask the agent for a Flux image
In Agent mode, describe the asset and name the model. The agent calls AiWings, runs Flux and shows the image in the chat before it touches any files.
Use Flux Fast to make a 4:5 clean product shot of peach-colored headphones on a soft pastel background, for the product card.Real, unedited Flux Fast results, the kind of placeholders and concepts an app needs:
Step 3: Save it into your project
This is where Cursor shines. Ask the agent to download the image into your assets folder and wire it into the code in the same request. You review the diff like any other change.
Save those four images to public/placeholders/ and use them as the card images in the Products grid until we have final photos.At one credit each, Flux Fast is ideal for filling a whole mock-up with real-looking images while you build, then swapping in finals later.
Flux Fast at a glance
AiWings offers Flux Fast, a draft-speed model that makes an image for a single credit. It works the same way everywhere you add it:
| Model | Sizes | Reference images | Cost per image | Best for |
|---|---|---|---|---|
| Flux Fast | 1K | None (text only) | 1 credit ($0.01) | Placeholders, concept art, clean product shots |
Prices are at the top-up rate of $0.01 per credit, and plans include more credits per dollar. At 1 credit ($0.01) an image you can try dozens of ideas for a dollar. To stop naming the model every time, say “make Flux Fast my default”.
Tips for app assets
- Use Flux Fast to fill layouts with real-looking images while you build, then swap in finals.
- Ask for several variations in one request and let the agent save the one you pick.
- Ask for the exact shape the layout needs: 4:5 for cards, 21:9 for banners.
- Flux Fast doesn’t edit existing files, so for edits use GPT Image or Nano Banana.
- Name files and folders in the request, and ask for WebP at the size you actually display.
If something doesn’t work
- The agent says it can’t make them: check that AiWings is enabled in Cursor Settings → MCP and that you’re in Agent mode.
- AiWings shows a red dot: click Connect again and finish the sign-in in your browser.
- No tools listed: check that the URL in mcp.json is exactly https://aiwings.io/api/mcp, then restart Cursor.
- Out of credits: top up from your AiWings dashboard, then ask the agent to try again.
Bottom line
Cursor can’t make images on its own, but with AiWings added as an MCP server, Flux becomes part of your build: generate the asset, save it and use it in your code in one request. The same server also gives Cursor GPT Image, Nano Banana, Imagen and Seedance video.
FAQ
Can Cursor use Flux natively?
No. Cursor doesn’t include Flux. You add it with AiWings, then ask for Flux Fast by name.
Which Flux model is it?
AiWings offers Flux Fast, a fast version built for drafts and quick ideas. It makes 1K images in about two seconds for a single credit.
Can Flux Fast edit my images?
No. Flux Fast makes images from a text prompt only. For edits, ask for a model that takes reference images, such as GPT Image, Nano Banana or Seedream, through the same connection.
Should I add it for one project or all of them?
Use ~/.cursor/mcp.json to add it to every project, or .cursor/mcp.json inside a repo to add it to that project only, for example to share the setup with your team.