Is your feature request related to a problem? Please describe.
I tried to add a MCP app via this gem. I was able to do it but it required me to create a subclass of MCP::Resources::TextContents which merged the _meta tag documented in https://apps.extensions.modelcontextprotocol.io/api/documents/csp-and-cors.html. I wonder if the _meta tag should be a first class citizen on the contents objects.
Describe the solution you'd like
Have a meta property like what already exists on the tool class but for contents.
Describe alternatives you've considered
The alternative solution was to just subclass the existing classes but having first class support would make shipping this easier.
Additional context
https://apps.extensions.modelcontextprotocol.io/api/documents/csp-and-cors.html describes why this is needed.
Is your feature request related to a problem? Please describe.
I tried to add a MCP app via this gem. I was able to do it but it required me to create a subclass of MCP::Resources::TextContents which merged the _meta tag documented in https://apps.extensions.modelcontextprotocol.io/api/documents/csp-and-cors.html. I wonder if the _meta tag should be a first class citizen on the contents objects.
Describe the solution you'd like
Have a meta property like what already exists on the tool class but for contents.
Describe alternatives you've considered
The alternative solution was to just subclass the existing classes but having first class support would make shipping this easier.
Additional context
https://apps.extensions.modelcontextprotocol.io/api/documents/csp-and-cors.html describes why this is needed.