Skip to main content
Glama

ModelScope Image MCP Server

English | 中文

An MCP (Model Context Protocol) server for generating images via the ModelScope image generation API. This server provides seamless integration with AI assistants, enabling them to create images through natural language prompts with robust async processing and local file management.

IMPORTANT: Earlier drafts of this README mentioned features like returning base64 data, negative prompts, and additional parameters. The current released code (see src/modelscope_image_mcp/server.py) implements a focused minimal feature set: one tool generate_image that submits an async task and saves the resulting image locally. Planned / upcoming features are listed in the roadmap below.

Current Features

  • Asynchronous image generation using ModelScope async task API

  • Periodic task status polling (every 5 seconds, up to 2 minutes)

  • Saves the first generated image to a local file

  • Returns task status and image URL to the MCP client

  • Robust error handling + timeout messaging

  • Simple one-command start with uvx

Related MCP server: Doubao Image/Video Generation MCP Server

Environment Variable

The server reads your credential from:

MODELSCOPE_SDK_TOKEN

If it is missing, the server will raise an error. Obtain a token from: https://modelscope.cn/my/myaccesstoken

Set on Windows (cmd):

set MODELSCOPE_SDK_TOKEN=your_token_here

PowerShell:

$env:MODELSCOPE_SDK_TOKEN="your_token_here"

Unix/macOS bash/zsh:

export MODELSCOPE_SDK_TOKEN=your_token_here

Installation & MCP Client Configuration

You can register the server directly in an MCP-compatible client (e.g. Claude Desktop) without a prior manual install thanks to uvx.

{
  "mcpServers": {
    "modelscope-image": {
      "command": "uvx",
      "args": ["modelscope-image-mcp"],
      "env": {
        "MODELSCOPE_SDK_TOKEN": "your_token_here"
      }
    }
  }
}

Option 2: Direct from GitHub

{
  "mcpServers": {
    "modelscope-image": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/zym9863/modelscope-image-mcp.git",
        "modelscope-image-mcp"
      ],
      "env": {
        "MODELSCOPE_SDK_TOKEN": "your_token_here"
      }
    }
  }
}

Option 3: Local Development Checkout

git clone https://github.com/zym9863/modelscope-image-mcp.git
cd modelscope-image-mcp
uv sync

Then configure MCP client entry using:

{
  "mcpServers": {
    "modelscope-image": {
      "command": "uvx",
      "args": ["--from", ".", "modelscope-image-mcp"],
      "env": { "MODELSCOPE_SDK_TOKEN": "your_token_here" }
    }
  }
}

Quick Local Smoke Test

# Run directly (local checkout)
uvx --from . modelscope-image-mcp

When running successfully you should see log lines showing task submission and polling.


## Usage Examples

### Basic Image Generation

```jsonc
{
  "name": "generate_image",
  "arguments": {
    "prompt": "A serene mountain landscape at sunset"
  }
}

Advanced Configuration

{
  "name": "generate_image",
  "arguments": {
    "prompt": "A futuristic city with flying cars, cyberpunk style",
    "model": "Qwen/Qwen-Image",
    "size": "1024x1024",
    "output_filename": "cyberpunk_city.png",
    "output_dir": "./generated_images"
  }
}

Creative Prompts

  • Art Style: "in the style of Van Gogh", "watercolor painting", "digital art"

  • Composition: "close-up portrait", "wide-angle landscape", "bird's eye view"

  • Lighting: "dramatic lighting", "golden hour", "studio lighting"

  • Mood: "mysterious atmosphere", "vibrant colors", "minimalist design"

Best Practices

  1. Be Specific: Detailed prompts produce better results than vague ones

  2. Use References: Mention specific art styles, artists, or time periods

  3. Experiment: Try variations of your prompt to find the best result

  4. Organize Outputs: Use descriptive filenames and organized directories

  5. Check Status: Monitor the async task status for long-running generations

generate_image

Creates an image from a text prompt using the ModelScope async API.

Parameters:

  • prompt (string, required): The text description of the desired image

  • model (string, optional, default: Qwen/Qwen-Image): Model name passed to API

  • size (string, optional, default: 1024x1024): Image resolution size, Qwen-Image supports: [64x64,1664x1664]

  • output_filename (string, optional, default: result_image.jpg): Local filename to save the first output image

  • output_dir (string, optional, default: ./outputs): Directory path where the image will be saved

Sample invocation (conceptual JSON sent by MCP client):

{
  "name": "generate_image",
  "arguments": {
    "prompt": "A golden cat playing in a garden",
    "size": "1024x1024",
    "output_filename": "cat.jpg",
    "output_dir": "./my_images"
  }
}

Sample textual response payload (returned to the client):

图片生成成功!
提示词: A golden cat playing in a garden
模型: Qwen/Qwen-Image
保存路径: /path/to/my_images/cat.jpg
输出目录: /path/to/my_images
文件名: cat.jpg
图片URL: https://.../generated_image.jpg

Notes:

  • Only the first image URL is used (if multiple are ever returned)

  • If the task fails or times out you receive a descriptive message

  • No base64 data is currently returned (roadmap item)

Internal Flow

  1. Submit async generation request with header X-ModelScope-Async-Mode: true

  2. Poll task endpoint /v1/tasks/{task_id} every 5 seconds (max 120 attempts ~= 2 minutes)

  3. On SUCCEED download first image and save via Pillow (PIL)

  4. Return textual metadata to MCP client

  5. Provide clear error / timeout messages otherwise

Roadmap

Planned enhancements (not yet implemented in server.py):

  • Optional base64 return data

  • Negative prompt & guidance parameters

  • Adjustable polling interval & timeout via arguments

  • Multiple image outputs selection

  • Streaming progress notifications

Development

# Install all (including dev) dependencies
uv sync --dev

# Run server module directly
uv run python -m modelscope_image_mcp.server

# Or via uvx using local source
uvx --from . modelscope-image-mcp

# Run with environment variable
MODELSCOPE_SDK_TOKEN=your_token_here uv run python -m modelscope_image_mcp.server

# Format code (if ruff is configured)
uv run ruff format .

# Lint code (if ruff is configured)
uv run ruff check . --fix

Project Structure

modelscope-image-mcp/
├── src/modelscope_image_mcp/
│   ├── __init__.py
│   └── server.py          # Main MCP server implementation
├── pyproject.toml         # Project configuration and dependencies
├── uv.lock               # Lock file for reproducible builds
├── README.md             # This file
└── README-zh.md         # Chinese documentation

Troubleshooting

Symptom

Possible Cause

Action

ValueError: 需要设置 MODELSCOPE_SDK_TOKEN 环境变量

Token missing

Export / set environment variable then restart

图片生成超时

Slow model processing

Re-run; later we will expose longer timeout argument

网络相关 httpx.TimeoutException

Connectivity issues

Check network / retry

PIL cannot identify image file

Invalid image data received

Try a different prompt or model

Permission denied when saving

Output directory permissions

Check write permissions or change output_dir

No such file or directory

Output directory doesn't exist

Server will create it automatically, or specify existing path

Changelog

1.0.1

  • Added size parameter support for customizable image resolution

  • Improved image generation with Qwen-Image model resolution range [64x64,1664x1664]

  • Enhanced documentation with size parameter usage examples

1.0.0

  • Major update with improved async handling and output directory support

  • Added configurable output directory parameter

  • Enhanced error handling and logging

  • Updated dependencies to use httpx for better async support

  • Fixed notification_options bug from initial release

0.1.0

  • Initial minimal implementation with async polling & local image save

  • Fixed bug: notification_options previously None causing AttributeError

License

MIT License

Contributing

PRs & issues welcome. Please describe reproduction steps for any failures.

Disclaimer

This is an unofficial integration example. Use at your own risk; abide by ModelScope Terms of Service.

Available Tools

1 tool
generate_imageC

使用ModelScope生成图片

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYes图片生成提示词
modelNo模型名称,默认为 Qwen/Qwen-ImageQwen/Qwen-Image
sizeNo生成图像分辨率大小,Qwen-Image支持:[64x64,1664x1664],默认为 '1024x1024'1024x1024
output_filenameNo输出图片文件名,默认为 'result_image.jpg'result_image.jpg
output_dirNo输出目录路径,默认为 './outputs'./outputs
poll_interval_secondsNo轮询基础间隔(秒),默认取环境变量或 5
max_poll_attemptsNo最大轮询次数,默认取环境变量或 120(约 10 分钟)
poll_backoffNo是否开启指数退避,默认取环境变量或 false
max_poll_interval_secondsNo指数退避的最大间隔(秒),默认取环境变量或 30

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions ModelScope but doesn't disclose traits like rate limits, authentication needs, cost implications, or what happens during generation (e.g., polling behavior implied by parameters). This leaves significant gaps for a tool with 9 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence, '使用ModelScope生成图片', which is front-loaded and wastes no words. However, it may be overly terse given the tool's complexity, potentially sacrificing clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, no output schema, no annotations), the description is incomplete. It lacks details on output format, error handling, or behavioral context, making it inadequate for an AI agent to fully understand how to invoke and interpret results effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 9 parameters. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage tips. Baseline 3 is appropriate as the schema handles the heavy lifting, but the description doesn't enhance understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '使用ModelScope生成图片' clearly states the action (generate) and resource (image) but is vague about specifics. It doesn't differentiate from siblings (none exist) but lacks detail about what ModelScope is or the generation process. It's functional but minimal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or context. The description only states what it does without any usage instructions or exclusions, leaving the agent to infer based on the tool name and parameters alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'generate_image' has a clearly distinct purpose that cannot be confused with any other tools in the set.

Naming Consistency5/5

With only one tool, naming consistency is inherently perfect. The tool name 'generate_image' follows a clear verb_noun pattern, and there are no other tools to create inconsistency with.

Tool Count2/5

A single tool for an image generation server is too minimal for the apparent scope. While image generation is a core function, typical image-related servers would include additional tools for variations, editing, or management tasks, making this feel incomplete.

Completeness2/5

The server is severely incomplete for an image generation domain. It only provides generation with no tools for editing images, creating variations, managing generated content, or handling different parameters or styles, which are common in such systems.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zym9863/modelscope-image-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server