MCP Qwen Image README | AllMCPs

Qwen Image MCP Server

Model Context Protocol server for Qwen Image 3 generation and editing through Ace Data Cloud.

Connect: hosted OAuth, API token, or local stdio

The hosted endpoint is https://qwen-image.mcp.acedata.cloud/mcp. Choose one route for the MCP client:

Route	When to use it	Credential setup
Hosted OAuth	The client supports remote MCP OAuth	Add only the URL, then sign in to AceDataCloud and approve access. No token needs to be pasted into client configuration.
Hosted API token	The client cannot finish OAuth, or you need an explicit integration credential	Send an AceDataCloud API token in the `Authorization: Bearer …` header. Keep it in a local secret store or environment variable.
Local stdio	The client runs a local MCP process	Install `mcp-qwen-image` and pass `ACEDATACLOUD_API_TOKEN` to that process. It still calls the AceDataCloud API.

The hosted service advertises OAuth metadata and Dynamic Client Registration (DCR). DCR registers the client application; it is not an API key. OAuth signs you in and the client sends the resulting Bearer token; it may reuse or create an API credential for the account. Browser sign-in still requires an AceDataCloud account. The hosted service can be metered: review current service documentation and displayed pricing before a real operation. Do not configure both an OAuth login and a fixed Authorization header for the same server.

Hosted OAuth examples

Claude and Claude Desktop chat: Add a remote custom connector in Customize → Connectors → Add custom connector, enter https://qwen-image.mcp.acedata.cloud/mcp, select sign-in, and choose Register automatically if Claude asks how to register its OAuth client. Complete consent. Claude Desktop's local claude_desktop_config.json is a separate setup. Claude connector guide.
Claude Code: claude mcp add --transport http --scope user qwen-image https://qwen-image.mcp.acedata.cloud/mcp, then claude mcp login qwen-image. Check /mcp. Claude Code MCP guide.
Cursor: Add a remote server with only https://qwen-image.mcp.acedata.cloud/mcp. For a project, merge the entry below into <project>/.cursor/mcp.json; for personal use, use ~/.cursor/mcp.json. Cursor MCP guide.
VS Code / Copilot: Run MCP: Add Server, select HTTP, enter https://qwen-image.mcp.acedata.cloud/mcp, then finish the browser sign-in. New portable workspace configs use <project>/.mcp.json; the VS Code-specific format below uses <project>/.vscode/mcp.json or the user profile. Check MCP: List Servers. VS Code MCP setup.
Codex: codex mcp add qwen-image --url https://qwen-image.mcp.acedata.cloud/mcp, then codex mcp login qwen-image. Its user settings are in ~/.codex/config.toml. Official Codex MCP guide.

Cursor project config (OAuth):

config.json

{
  "mcpServers": {
    "qwen-image": {"url": "https://qwen-image.mcp.acedata.cloud/mcp"}
  }
}

VS Code-specific workspace config (OAuth):

config.json

{
  "servers": {
    "qwen-image": {"type": "http", "url": "https://qwen-image.mcp.acedata.cloud/mcp"}
  }
}

Hosted API token

Sign in at AceDataCloud Platform, open the service page, and obtain an API credential. A fixed Bearer header is useful when your client lacks OAuth; an invalid header does not fall back to OAuth in Claude Code. The header value is sensitive, so keep it out of committed files and screenshots.

For Claude Code, the shell expands the token when you add the server; treat the saved user MCP config as a secret:

server.ts

export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
claude mcp add --transport http --scope user qwen-image https://qwen-image.mcp.acedata.cloud/mcp \
  --header "Authorization: Bearer $ACEDATACLOUD_API_TOKEN"

For a Claude Code project config, put a variable reference in <project>/.mcp.json and set that variable in the environment that launches Claude Code:

config.json

{
  "mcpServers": {
    "qwen-image": {
      "type": "http",
      "url": "https://qwen-image.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${ACEDATACLOUD_API_TOKEN}"}
    }
  }
}

Cursor uses a different environment-variable syntax in ~/.cursor/mcp.json or an uncommitted project config:

config.json

{
  "mcpServers": {
    "qwen-image": {
      "url": "https://qwen-image.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${env:ACEDATACLOUD_API_TOKEN}"}
    }
  }
}

In VS Code, run MCP: Open User Configuration and merge this server plus its masked input; ${input:...} is for VS Code's user/workspace format and is not portable to the Agent Host .mcp.json format:

config.json

{
  "inputs": [
    {"id": "acedata-qwen-image-token", "type": "promptString", "description": "AceDataCloud API token", "password": true}
  ],
  "servers": {
    "qwen-image": {
      "type": "http",
      "url": "https://qwen-image.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${input:acedata-qwen-image-token}"}
    }
  }
}

For Cline, use its MCP configuration UI or CLI file ~/.cline/data/settings/cline_mcp_settings.json; its remote transport value is streamableHttp. For JetBrains AI Assistant, add a remote URL from Settings → Tools → AI Assistant → Model Context Protocol (MCP). For Zed, use a context_servers entry with the URL only for OAuth or add a local Bearer header. These clients have different configuration schemas; follow their current UI rather than copying another client's JSON. Cline · JetBrains · Zed.

Local stdio

Install the package and give the local process an API token:

server.ts

python -m pip install mcp-qwen-image
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-qwen-image

For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (~/Library/Application Support/Claude/claude_desktop_config.json on macOS). uvx requires uv on PATH:

config.json

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

Keep this user-level file private. Self-hosted HTTP uses mcp-qwen-image --transport http --port 8000; expose it only with suitable network and TLS controls. Local execution still calls the AceDataCloud API.

Check before using the service

https://qwen-image.mcp.acedata.cloud/health returning {"status":"ok"} checks endpoint reachability only.
Confirm that the MCP client loads tools. qwen_image_list_models is a reference tool; it does not verify downstream API access or balance.
Use a documented service operation for an end-to-end check after reviewing current service documentation and displayed pricing. If the result contains a task ID, call qwen_image_get_task on that same ID until terminal success or failure. Do not resubmit the operation just to check progress.

For 401, check which auth route the client used and whether the token or OAuth session is valid. A 403 may mean an account permission or content moderation failure; read the returned error. Insufficient balance and downstream service failures need their own diagnosis. A listed tool or submitted task does not prove a successful result.

Tools

Tool	Purpose
`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

Models: qwen-image-3.0 (default) and qwen-image-3.0-pro.