Source note · Model Context Protocol transports compared
In MCP revision 2026-07-28 a transport binding MUST deliver client-sent requests and notifications to the server and server-sent responses and notifications to the client; no other message direction exists, so servers do not initiate JSON-RPC requests and clients do not send JSON-RPC responses.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- transports
- Deployment
- local-subprocess, remote-http, 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 Messages, second paragraph
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-message-directions. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-message-directions
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-message-directions,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-message-directions},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-message-directions},
note = {Source note mcp-transport-differences-message-directions, checked 2026-09-30}
}