Skip to content

docs: explain how MCP servers actually launch (stdio vs SSE, Inspector)#4091

Open
TanishkaMarrott wants to merge 1 commit intomodelcontextprotocol:mainfrom
TanishkaMarrott:docs/how-mcp-servers-run-521
Open

docs: explain how MCP servers actually launch (stdio vs SSE, Inspector)#4091
TanishkaMarrott wants to merge 1 commit intomodelcontextprotocol:mainfrom
TanishkaMarrott:docs/how-mcp-servers-run-521

Conversation

@TanishkaMarrott
Copy link
Copy Markdown

Summary

Closes #521 — addresses the recurring confusion around running MCP servers.

  • Adds a "Understanding How Servers Are Launched" subsection inside Getting Started, between the standalone npx/uvx examples and the client config section
  • Explains that stdio servers block on stdin by design — running one directly in a terminal will look like a hang, which is expected
  • Clarifies that the MCP client spawns the server; the config file is the trigger, not a manual uvx command
  • Adds a two-row table contrasting stdio vs SSE/HTTP transport so readers can see at a glance which mode applies to them
  • Points to the MCP Inspector (npx @modelcontextprotocol/inspector uvx mcp-server-git) as the recommended way to test a server locally without wiring up a full client

No existing content changed. The new subsection slots in cleanly between the two existing subsections.

Test plan

  • Read the new subsection — confirm it answers the three questions in confusing documentation #521 (why the server appears to hang, who actually spawns the process, how to test without a full client)
  • Verify the Inspector command renders correctly in GitHub markdown
  • Confirm the table renders in GitHub markdown preview

🤖 Generated with Claude Code

Closes a recurring point of confusion (modelcontextprotocol#521): developers run
`uvx mcp-server-git` directly, see no output, and think the server
is broken. Added a new 'Understanding How Servers Are Launched'
subsection that explains:

- stdio servers wait on stdin — appearing to hang is expected
- the MCP client spawns the server; you don't run it yourself
- stdio vs SSE/HTTP transport comparison table
- MCP Inspector as the recommended local testing tool

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown

@alialobidm alialobidm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

``

@TanishkaMarrott
Copy link
Copy Markdown
Author

/i-promise-this-is-not-a-new-server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

confusing documentation

2 participants