The surface is deliberately minimal — prompt in, image out — and the suffix setting is the detail that saves repetition, since the model version rides along with every request automatically. Weigh the auth model before installing: session tokens are more sensitive than a scoped API key, and there is no separate service account here.
A small MCP server that puts Midjourney image generation behind a single tool call. It authenticates with your own Midjourney session tokens rather than an API key, and appends a version suffix to every prompt so the model version is set once in configuration instead of repeated in each request.
- An image generated from a text description and an aspect ratio such as `16:9`, returned as a string — `generating_image`
- A default suffix appended to every prompt, `--v 6.1` unless you override `SUFFIX`, so the model version is a configuration decision
- An overridable endpoint through `API_BASE`, which defaults to `midjourney.com`
Your own Midjourney authentication, supplied as the two session tokens `TOKEN_R` and `TOKEN_I` — not an issued API key, which means the credential is tied to your logged-in session and generation bills to your Midjourney plan. `API_BASE` and `SUFFIX` are optional. Run it with `uvx midjourney-mcp` over stdio. The project is licensed GPL-3.0, which is stricter than most servers in this category and matters if you plan to embed it.
One command plus a key — uvx midjourney-mcp, then supply credentials
