[DOCS] MCP docs missing non-blocking startup behavior for `claude "prompt"`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/mcp

Section/Topic

MCP server startup behavior for sessions launched with claude "query", especially the "Managing your servers" and "Use MCP servers from Claude.ai" sections

Current Documentation

The docs currently say:

In the CLI reference: | claude "query" | Start interactive session with initial prompt | claude "explain this project" |

In the MCP docs: If you've logged into Claude Code with a Claude.ai account, MCP servers you've added in Claude.ai are automatically available in Claude Code: In Claude Code, use the command: /mcp Claude.ai servers appear in the list with indicators showing they come from Claude.ai.

Also in the MCP docs: * Automatic lifecycle: At session startup, servers for enabled plugins connect automatically. If you enable or disable a plugin during a session, run /reload-plugins to connect or disconnect its MCP servers

These sections explain how to start an interactive session with an initial prompt and how to view/manage MCP servers, but they do not explain what users should expect during startup when MCP servers are still connecting.

What's Wrong or Missing?

Changelog v2.1.84 changed the startup behavior for claude "prompt" with MCP servers: the REPL now renders immediately instead of waiting for all server connections to finish.

The docs do not explain that:

A. The interactive prompt can appear before all MCP servers are connected

Users can now land in the REPL while MCP startup is still in progress.

B. MCP capabilities may appear progressively

Tools, prompts, and resources from MCP servers may not all be available at the exact moment the REPL first appears.

C. /mcp is the place to verify connection status

The docs mention /mcp for management, but they do not connect it to this startup lifecycle or tell users to use it when MCP functionality is not available immediately after launch.

Without this explanation, the new non-blocking behavior can look like a partial MCP failure instead of intentional startup behavior.

Suggested Improvement

Add a short startup-behavior note to https://code.claude.com/docs/en/mcp near the server management/startup sections, for example:

Claude Code does not block the interactive prompt while MCP servers connect. When you start a session with claude "query" (or claude), the REPL can appear immediately and MCP servers continue connecting in the background. Use /mcp to check connection status if an MCP tool, prompt, or resource is not available yet.

Add a brief cross-reference in https://code.claude.com/docs/en/cli-reference for the claude "query" row so users know prompt-started sessions with MCP servers do not wait for every connection before rendering the REPL.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/mcp | MCP server management and startup lifecycle |
| https://code.claude.com/docs/en/cli-reference | claude "query" launch behavior for interactive sessions with an initial prompt |

Total scope: 2 pages affected

Source: Changelog v2.1.84

Exact changelog entry:

Improved startup for claude "prompt" with MCP servers — the REPL now renders immediately instead of blocking until all servers connect