claude-code - 💡(How to fix) Fix MCP tool results should support the native Edit tool's diff rendering [1 comments, 2 participants]

TL;DR

Allow MCP tools to opt into the native Edit tool's diff rendering by adding a content-type annotation to TextContent.

Guidance

• Investigate adding a content-type annotation to TextContent to signal that the result is a diff, enabling Claude Code to render it as a colored unified diff.
• Review related issues, such as #22619 and #18177, to understand existing efforts towards improving tool integration and diff rendering.
• Consider the display/context separation concept from #15718, although it's closed, to inform the design of the diff rendering feature.
• Evaluate the feasibility of introducing a new content-type annotation, ensuring it aligns with the existing architecture and doesn't introduce compatibility issues.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The solution relies on the assumption that adding a content-type annotation to TextContent is technically feasible and aligns with the existing Claude Code architecture. The implementation details and potential compatibility implications need to be carefully considered.

Recommendation

Apply a workaround by introducing a content-type annotation to TextContent, allowing MCP tools to opt into the native Edit tool's diff rendering, as this addresses the primary user complaint and provides a clear path forward.