{"version":"2.1.247","anchor":"claude-mcp-serve-has-a-result-format-parameter-wired-but-no-","canonical_anchor":"claude-mcp-serve-has-a-result-format-parameter-wired-but-no-","heading":"claude mcp serve has a result-format parameter wired but no way to set it","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/claude-mcp-serve-has-a-result-format-parameter-wired-but-no-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### `claude mcp serve` has a result-format parameter wired but no way to set it\n\nThe MCP server can take a result format, but the only caller hardcodes raw.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The server is invoked with `\"raw\"` as a fixed fifth argument, so the parameter the entry point accepts is never actually consulted.\n- A local variable holding the result format, defaulted to `\"raw\"`, is declared and then never read.\n- No command-line flag, environment variable or settings key exposes the option, so no caller can supply a value other than the default.\n- 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.\n\n**Evidence**\n\n`await f(l, c ?? !1, e ?? !1, s, \"raw\");`, `resultFormat`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}