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

[TanishkaMarrott]

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

[TanishkaMarrott]

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

[TanishkaMarrott]

@cliffhall — this is a docs-only fix to README.md (21 lines added, no new servers). It closes #521 which has been open for a while. The CI failure is a permissions error on the bot's side, not an issue with the PR itself — the branch only touches README.md. Would appreciate a quick look when you have bandwidth!

[MukundaKatta]

+1, this would have saved me time. I was just writing READMEs for some
stdio MCP servers and my own confidence-test was running npx -y <package>
in a terminal, then being confused by the silence for half a minute. The
two-row stdio vs SSE table is the right level. Tiny ask: an explicit
"if nothing prints, that's correct" line right above the standalone npx
example.

[TanishkaMarrott]

Thanks @MukundaKatta — good call. I've added an explicit note right above the standalone npx example: 'If you run this command and see no output, that is correct — the server is waiting for a client to connect over stdin.' It also links down to the Understanding How Servers Are Launched section for full context.