Skip to content

v1.21.3 - MCP JSON UTF-8 body fix

Latest

Choose a tag to compare

@Tefx Tefx released this 13 Sep 09:30

Fixed

  • MCP tool JSON bodies emit non-ASCII characters as UTF-8 text instead of \uXXXX escapes, so clients that concatenate TextContent.text receive readable CJK and emoji without a second JSON parse.

Unpaired surrogates still fall back to ASCII escaping so MCP UTF-8 framing does not crash.