MCP Configuration
MCP transport type mismatch
MCP servers communicate over a specific transport — commonly stdio for local processes, or HTTP/SSE for remote ones — and the config has to match what the server actually speaks.
A local server you start as a subprocess almost always uses stdio; a hosted server you connect to over the network uses HTTP or SSE instead. Configuring the wrong one for a given server is a common reason it never connects, even though the command or URL itself is correct.
The server's own documentation will state which transport it expects — that's the source of truth, not a guess based on how similar servers are usually configured.
This is one of the first things worth double-checking when a server fails silently with no clear error: right command or URL, wrong transport type.
Check the server's documentation for which transport (stdio, HTTP, SSE) it expectsFrequently asked questions
What does MCP transport type mismatch do in Claude Code?
MCP servers communicate over a specific transport — commonly stdio for local processes, or HTTP/SSE for remote ones — and the config has to match what the server actually speaks.
How do I use it?
Try: Check the server's documentation for which transport (stdio, HTTP, SSE) it expects
Any caveats to know about?
This is one of the first things worth double-checking when a server fails silently with no clear error: right command or URL, wrong transport type.
Is this covered in the Claude Code Toolkit?
Yes — MCP transport type mismatch and patterns like it are part of the full command, hook, and template pack included with a Claude Code Toolkit subscription.
Want the full command, hook, and template pack?
This is one pattern out of the full Claude Code Toolkit — subscribe for the complete set, plus everything we add going forward.
Subscribe to the toolkit — $79/mo