Source note · Model Context Protocol transports compared
In MCP revision 2026-07-28 custom transports MUST preserve the JSON-RPC message format, the message patterns and the per-request metadata model, and custom transports that run over a reliable bidirectional byte stream such as Unix domain sockets or TCP SHOULD reuse the stdio framing.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- custom transports
- Deployment
- custom-transport
- Region
- not restricted
- Release range
- MCP revision 2026-07-28
- Checked
- 2026-09-30
Sources
- Overview (Transports) - MCP specification revision 2026-07-28 — Model Context Protocol project · tier 1 standards and regulators · section Custom Transports, second and third paragraphs
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-custom-transport-rules. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-custom-transport-rules
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-custom-transport-rules,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-custom-transport-rules},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-custom-transport-rules},
note = {Source note mcp-transport-differences-custom-transport-rules, checked 2026-09-30}
}