Skip to main content
Glama
runapi-ai

RunAPI Qwen Image MCP Server

Official
by runapi-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RUNAPI_API_KEYNoAPI key for RunAPI, used for headless and CI hosts. Resolves auth before the config file.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

edit_imageB

Create a Qwen Image task on RunAPI (edit image). Returns a task id, status, and output URLs.

remix_imageA

Create a Qwen Image task on RunAPI (remix image). Returns a task id, status, and output URLs.

text_to_imageB

Create a Qwen Image task on RunAPI (text to image). Returns a task id, status, and output URLs.

get_taskB

Fetch the current status and latest result payload for a qwen-image task.

check_pricingB

Look up RunAPI pricing for the qwen-image model line.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation4/5

The three image generation tools (text_to_image, edit_image, remix_image) could be confused since they all create Qwen Image tasks returning similar payloads, but their action-prefix names do clearly distinguish the three modes. login, get_task, and check_pricing are distinct concerns. Only the generation trio has mild boundary ambiguity.

Naming Consistency5/5

All tools consistently follow a clear snake_case verb-first convention: login, edit_image, remix_image, text_to_image (verb or noun phrase prefix), get_task, check_pricing. There is a uniform action-oriented pattern with no mixed casing or style deviations.

Tool Count5/5

Six tools is a well-scoped surface for an image-generation API wrapper: auth, three generation modes, task status polling, and pricing lookup. Each tool earns its place and none feel redundant or unnecessary.

Completeness4/5

The surface covers the core lifecycle: authentication, generation in three modes, task polling, and pricing. Minor gaps exist—no explicit cancel/delete task or batch operations—but the primary workflows are fully supported and there are no dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues