# mcp-qwen-image [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/AceDataCloud/QwenImageMCP  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-qwen-image

## Description
MCP server for Qwen Image 3 AI image generation

## Tools
Capabilities this server exposes over MCP:

- **qwen_image_generate** — Generate 1–6 images from text
- **qwen_image_edit** — Edit with 1–3 reference images
- **qwen_image_get_task** — Query one asynchronous task
- **qwen_image_get_tasks_batch** — Query multiple tasks
- **qwen_image_list_models** — Compare Standard and Pro

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-qwen-image": {
    "command": "uvx",
    "args": ["mcp-qwen-image"],
    "env": {
      "ACEDATACLOUD_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `ACEDATACLOUD_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What mcp-qwen-image MCP server does

The mcp-qwen-image MCP server exposes Ace Data Cloud's Qwen Image 3 service through the Model Context Protocol. It supports creating images from text, modifying existing images with references, checking asynchronous operations, and comparing the available Standard and Pro models.

The available models are `qwen-image-3.0`, which is the default, and `qwen-image-3.0-pro`. Generation requests can return between one and six images. Editing requests accept between one and three reference images.

## How it works

MCP clients can connect to the hosted endpoint at `https://qwen-image.mcp.acedata.cloud/mcp`. Hosted access supports either browser-based OAuth or an Ace Data Cloud API token sent as a Bearer credential. OAuth requires an Ace Data Cloud account and client consent; it does not require putting a token in the client configuration.

A local installation runs over stdio and uses the `mcp-qwen-image` command. Local execution does not make the service self-contained: requests continue to use the Ace Data Cloud API. The package can also start an HTTP transport locally with a specified port, but network exposure and TLS remain the operator's responsibility.

Image operations may be asynchronous. After an operation returns a task ID, use `qwen_image_get_task` to check that task until it reaches a terminal state. `qwen_image_get_tasks_batch` provides status checks for multiple tasks. Repeating the original generation or editing request is not the appropriate way to check progress.

## Setup and configuration

For local stdio use, install the package with `python -m pip install mcp-qwen-image`, set `ACEDATACLOUD_API_TOKEN`, and run `mcp-qwen-image`. Claude Desktop can launch it through `uvx`, provided that `uv` is installed and available on `PATH`.

For hosted OAuth, configure only the hosted URL and complete the sign-in flow in the client. For token-based access, send `Authorization: Bearer` with the API token. Do not configure OAuth and a fixed authorization header for the same server. Keep tokens out of committed files, screenshots, and shared configuration.

The README documents setup for Claude Desktop, Claude Code, Cursor, VS Code, Codex, Cline, JetBrains AI Assistant, and Zed. Their configuration formats differ, so use the client-specific schema rather than copying a configuration from another client.

## Tools and capabilities

- `qwen_image_generate`: creates one to six images from a text prompt.
- `qwen_image_edit`: edits images using one to three reference images.
- `qwen_image_get_task`: checks one asynchronous task.
- `qwen_image_get_tasks_batch`: checks several asynchronous tasks.
- `qwen_image_list_models`: lists or compares the Standard and Pro model options.

## Limitations and notes

The mcp-qwen-image MCP server depends on Ace Data Cloud for processing, authentication, account access, and service availability. Hosted operations may be metered, so review the current service documentation and displayed pricing before making real requests.

The `/health` endpoint only checks whether the hosted endpoint is reachable. Loading the tools or calling `qwen_image_list_models` does not confirm downstream API access, account balance, or a successful image operation. A 401 generally requires checking the selected authentication route and credential; a 403 can indicate account permissions or content moderation. Balance problems and downstream failures require separate diagnosis.

A successful tool listing or submitted task is not proof that an image was produced. Check returned task IDs and read terminal errors before treating an operation as complete.

_Full upstream README: https://allmcps.com/mcp/mcp-qwen-image/readme_