Midjourney

MidjourneyMCP

A Model Context Protocol (MCP) server for AI image and video generation using Midjourney through the AceDataCloud API.

Generate AI images, videos, and manage creative projects directly from Claude, VS Code, or any MCP-compatible client.

Features

• Image Generation - Create AI-generated images from text prompts
• Image Transformation - Upscale, create variations, zoom, and pan images
• Image Blending - Combine multiple images into creative fusions
• Reference-Based Generation - Use existing images as inspiration
• Image Description - Get AI descriptions of images (reverse prompt)
• Image Editing - Edit images with text prompts and masks
• Video Generation - Create videos from text and reference images
• Video Extension - Extend existing videos to make them longer
• Translation - Translate Chinese prompts to English
• Task Tracking - Monitor generation progress and retrieve results

Tool Reference

Verify the connection before generating

After installation, discover the server's tools and call midjourney_list_actions with no arguments. This reference tool returns locally defined model or action information without calling a generation API. It does not validate your application key, account balance, service access, or current price. Your client's Chat model can still create separate charges.

To check authenticated access without creating media, query a task already owned by your application using the task-lookup tool and the same original task ID. If you have no existing task, stop after discovery/reference output; do not generate media just to test installation. Review current pricing before any new generation.

For missing tools, reconnect and refresh the tool list. For 401/403, check the existing application's key, service permissions, Allowed APIs, expiration and usage limit before replacing credentials. Keep a task/trace ID for other failures, never your key; do not automatically retry a paid operation.

Connect: hosted OAuth, API token, or local stdio

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

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://midjourney.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 midjourney https://midjourney.mcp.acedata.cloud/mcp, then claude mcp login midjourney. Check /mcp. Claude Code MCP guide.
• Cursor: Add a remote server with only https://midjourney.mcp.acedata.cloud/mcp. For a project, merge the entry below into /.cursor/mcp.json; for personal use, use ~/.cursor/mcp.json. Cursor MCP guide.
• VS Code / Copilot: Run MCP: Add Server, select HTTP, enter https://midjourney.mcp.acedata.cloud/mcp, then finish the browser sign-in. New portable workspace configs use /.mcp.json; the VS Code-specific format below uses /.vscode/mcp.json or the user profile. Check MCP: List Servers. VS Code MCP setup.
• Codex: codex mcp add midjourney --url https://midjourney.mcp.acedata.cloud/mcp, then codex mcp login midjourney. Its user settings are in ~/.codex/config.toml. Official Codex MCP guide.

Cursor project config (OAuth):

{

"mcpServers": { "midjourney": {"url": "https://midjourney.mcp.acedata.cloud/mcp"} } }

VS Code-specific workspace config (OAuth):

{

"servers": { "midjourney": {"type": "http", "url": "https://midjourney.mcp.acedata.cloud/mcp"} } }

Hosted API token

1. Open Ace Data Cloud → Applications. Sign in, or register an account first.
2. Find General application. If it has not been created, choose Initialize General Application. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and current pricing.
3. Copy the API Key from the application card, or open Keys / Manage Keys → Create to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
4. When creating a key, review Expiration Time, Set Usage Limitation, and Allowed APIs. Enable only the restrictions you need, allow the operations you will call, then click Create and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
5. Copy only the token value, without quotation marks, spaces, or Bearer . An API Key / API Token field expects this raw value; only a manually configured HTTP Authorization header needs the Bearer prefix. A platform-... account-management token cannot replace a generation API key.

Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.

A fixed Bearer header bypasses OAuth. If the header is invalid, remove it before trying browser sign-in; keep the saved credential private.

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

export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'

claude mcp add --transport http --scope user midjourney https://midjourney.mcp.acedata.cloud/mcp \ --header "Authorization: Bearer $ACEDATACLOUD_API_TOKEN"

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

{

"mcpServers": { "midjourney": { "type": "http", "url": "https://midjourney.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:

{

"mcpServers": { "midjourney": { "url": "https://midjourney.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:

{

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