How to Generate Images in Claude (2026 Guide)

Claude is a large language model product. Chat, coding, analysis, and long documents are first-class. Raster image models (and the infrastructure to run them) are a different stack. Anthropic’s product surface for Claude.ai focuses on conversation and tools Claude can call, not a built-in paint button.

That is intentional architecture, not a glitch. Tools such as calculators, browsers, or remote MCP servers plug into the chat when you authorize them. Image generation fits the same pattern: Claude plans the prompt; a connected image service renders the pixels.

Claude Connectors let you attach remote services that expose tools Claude can call. Under the hood this often uses the Model Context Protocol (MCP): a standard way for hosts (Claude) to discover tools, authenticate with OAuth, and run actions during a conversation.

For images, that means Claude can open an upload widget, call generate_image with your description, and return a result in the same thread, then edit the last result with a follow-up like “make the background cleaner.”

• You add a custom connector URL once (for AiWings: your MCP endpoint).
• You sign in and authorize access to your credits and generation tools.
• You ask for images in plain language in any chat that has the connector enabled.

AiWings is built so image work stays inside Claude. Connect once from the dashboard, authorize OAuth, and Claude can create, reference-upload, and edit images using your AiWings credit balance, without hopping to a separate image studio for every revision.

• Generate from text prompts in the chat you are already in.
• Upload product or face references when you need consistency.
• Iterate with follow-ups (“warmer light,” “square crop,” “same bottle, studio background”).
• Use model and resolution defaults from your AiWings dashboard.

High level only. Step-by-step with screenshots-style checklists lives in our dedicated connect guide.

1. Create or sign in to an AiWings account and buy credits if you need more balance.
2. Copy the MCP connector URL from AiWings (dashboard or connect guide).
3. In Claude, open Settings, Connectors, Add custom connector and paste the URL.
4. Complete the browser authorize flow when Claude prompts you.
5. In a new chat, ask for an image and let Claude call AiWings tools.

Follow the full connect checklist

Be concrete about subject, style, lighting, and aspect. When you care about a real product or person, say you have a photo to upload so Claude can open the reference upload flow first.

• “Generate a risograph-style poster of layered mountains at sunset, vertical poster ratio.”
• “I will upload our bottle photo, then place it on a marble pedestal in soft studio light.”
• “Edit the last image: cooler palette, less clutter in the background.”

Image runs consume credits based on model and resolution. Higher quality and larger sizes cost more. Set defaults in the AiWings dashboard so Claude does not re-ask every time, and override only when a one-off needs a different look.

• Pasting a URL that redirects (for example www redirecting to apex). Claude’s MCP client needs a host that serves the endpoint directly.
• Expecting Claude to “draw” with code or ASCII when an image connector is disabled.
• Re-uploading a previous result URL by hand instead of asking Claude to edit the last generation.

In 2026, generating images “in Claude” means attaching image tools Claude can call, not waiting for a secret native button. Connectors plus AiWings close that gap so creation and edits stay in one conversational thread.