feat: Add resource_link content type support to ToolResults component

[nandsha]

Add ResourceLinkView component for displaying Resource links

Motivation and Context

Adds support for the new resource_link content type. Previously, Resource links in tool results were showing as Invalid Tool Result because the Inspector's ToolResults component lacked rendering support for Resource link.

How Has This Been Tested?

Created test MCP server that returns resource_link content in tool results and verified Resource link display correctly with URI, name, description, and mimeType

Breaking Changes

None. This is a purely additive change that adds support for displaying a new content type.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

• Implements new resource_link content type support from MCP protocol
• Added ResourceLinkView component
• Progressive disclosure for optional metadata (name, description, mimeType)
• Updated ToolResults.tsx with test coverage for Resource link type

Fixes #553

[richardkmichael]

#530 is also about ResourceLink

[olaservo]

Heads up there was a change added to the Everything reference server recently to include an example of Resource links: modelcontextprotocol/servers#2276

However it has not yet been released to NPM. Will follow up here once that happens. (Typically it takes 1-2 days after merge, since someone from the core team needs to approve publishing the package after a scheduled job runs.)

[cliffhall]

This is absolutely lovely, however, the links themselves actually go nowhere, because it's a URI within the MCP server itself. Clicking them just opens a new tab that doesn't render anything.

What would be perfect would be to send the user to the resources tab and open the given resource with a resources/read request.

Alternatively, this component could send the request, get the result and open a DynamicJSONForm to display the resource in-place.

[cliffhall]

BTW, you can also test this with the latest version of the getResourceLinks tool of the Everything server.

[nandsha]

Thanks for the great feedback! Working on the refinements, making use of the latest Everything server.

[nandsha]

Extended the initial Resource Link support with a more comprehensive implementation that addresses @cliffhall's suggestions (alternative approach) for enhanced link functionality. Resource links now send resources/read requests when clicked, and the content appears inline directly in the tool results using JsonView component.

resource_link_view.mov

[nandsha]

In addition, added test coverage for Resource Link. Thanks @cliffhall and @olaservo

[cliffhall]

LGTM! 👍

Thanks @nandsha! This was the perfect implementation. 👌