The MCP server can take a result format, but the only caller hardcodes raw.
claude mcp serve accepts a result-format option that is passed the literal string raw and appears nowhere else.
What's wrong with this entry?
The MCP server entry point now takes a result format and passes one down to the server it starts, laying the groundwork for output other than raw. In this build the value is hardcoded: the only caller passes the literal string "raw", and the name appears exactly once in the whole bundle, at the point where it is unpacked from the options object. Running claude mcp serve behaves exactly as before.
- The server is invoked with
"raw"as a fixed fifth argument, so the parameter the entry point accepts is never actually consulted. - A local variable holding the result format, defaulted to
"raw", is declared and then never read. - No command-line flag, environment variable or settings key exposes the option, so no caller can supply a value other than the default.
- Nothing in the build handles a non-raw format yet, so this is groundwork only rather than a switched-off feature you could turn on.
await f(l, c ?? !1, e ?? !1, s, "raw");, resultFormat
Strings lifted out of the shipped bundle, so the claim above can be checked against them.