Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

claude mcp serve has a result-format parameter wired but no way to set it

The MCP server can take a result format, but the only caller hardcodes raw.

Nothing to try yet In Development
JSON All of v2.1.247
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.247,
In DevelopmentSection of the release

claude mcp serve accepts a result-format option that is passed the literal string raw and appears nowhere else.

What

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.

Details
  • 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.
Evidence

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.

See this entry in the whole of v2.1.247 →

Feedback