Source note · Model Context Protocol transports compared
MCP JSON-RPC messages MUST be UTF-8 encoded regardless of transport.
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 revisions 2025-03-26 through 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, first paragraph
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-utf8-encoding. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-utf8-encoding
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-utf8-encoding,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-utf8-encoding},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-utf8-encoding},
note = {Source note mcp-transport-differences-utf8-encoding, checked 2026-09-30}
}