midjourney-mcp-web
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUFFIX | No | Parameters appended to every prompt | --v 8.1 |
| TOKEN_I | Yes | Value of __Host-Midjourney.AuthUserTokenV3_i cookie | |
| TOKEN_R | Yes | Value of __Host-Midjourney.AuthUserTokenV3_r cookie | |
| API_BASE | No | Midjourney web host | www.midjourney.com |
| CHANNEL_ID | No | Override channel id | singleplayer_<user_id> |
| MJ_JOB_TIMEOUT_SEC | No | Polling timeout for completed job visibility | 300 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generating_imageB | Generate an image with Midjourney. Args: prompt: English image prompt. Additional Midjourney parameters can be included. aspect_ratio: Aspect ratio such as "16:9", "4:3", or "3:4". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
The single tool uses a descriptive verb_noun pattern ('generating_image'), and there is no inconsistency since there's only one tool.
One tool is on the borderline of being too few for a domain like image generation, which typically benefits from additional capabilities (e.g., describing, varying). However, it may suffice for basic generation.
The tool surface is severely limited to only generation, lacking common lifecycle operations like retrieving results, upscaling, or modifying images. This will likely lead to agent failures in practical workflows.