Midjourney MCP Server

midjourney_open

Open a Midjourney page in your signed-in Cloud Browser to generate, vary, upscale, animate, and organize images and videos using your existing account session.

Instructions

Open a Midjourney page in your signed-in Cloud Browser (default https://midjourney.com) to work with generate, vary, upscale, animate and organize images and videos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "midjourney_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://midjourney.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the page opens in a signed-in Cloud Browser session, which tells the agent auth state is handled. It does not state whether this reuses or creates a tab, what happens with an invalid URL, or what the caller receives back, which matters for chaining into sibling tools.

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?

One sentence, front-loaded with the action and default URL. The capability list at the end is somewhat loose since those operations belong to sibling tools rather than this one, but it is not wasteful enough to hurt much.

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

Completeness4/5

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

A single optional parameter, no annotations, no output schema — the surface is small and the description covers the action, default, and session context adequately. Slightly incomplete on what happens after the page opens, but not required for correct invocation.

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 coverage is 100% and the single url parameter is documented in the schema with the same default shown in the description. The description adds no meaning beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

Specific verb and resource: 'Open a Midjourney page in your signed-in Cloud Browser.' The parenthetical default URL anchors it precisely. It does not explicitly differentiate itself from siblings like midjourney_close or midjourney_status beyond the implicit verb 'open'.

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

Usage Guidelines3/5

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

The trailing clause 'to work with generate, vary, upscale, animate and organize images and videos' implies this is the entry point before operating on the page, but usage is only inferred. There is no explicit when-to-use, no prerequisites, and no named alternative to route away from.

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

Deploy Server