{"version":"2.1.314","anchor":"stream-json-mcp-serve-path-adds-a-no-answer-acknowledgement","canonical_anchor":"stream-json-mcp-serve-path-adds-a-no-answer-acknowledgement","heading":"MCP server mode returns a clear result when a permission request is declined","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/stream-json-mcp-serve-path-adds-a-no-answer-acknowledgement","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### MCP server mode returns a clear result when a permission request is declined\n\nWith `CLAUDE_CODE_MCP_SERVE_TOOL_OUTPUT` on, a declined or withdrawn permission request now returns a result saying nothing was run\n\n**What**\n\nClaude Code can act as an MCP server, which means another program can connect to it and call its tools. Sometimes a tool call needs permission first. When `CLAUDE_CODE_MCP_SERVE_TOOL_OUTPUT` is turned on and that permission question is answered with a no, or withdrawn, the connected program now gets a result marked \"acknowledged\" with the text: \"Nothing was run: the permission question was answered with a no, or taken back.\"\n\n**Why**\n\nPrograms connected to Claude Code get a defined answer when a permission request is declined, so they can tell that nothing ran.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}