You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Setting a mime type on a Ressource using FastMCP is being ignored by the low level server as the returned type is based on the ReadResourceRequest result type.
To Reproduce
Create any resource that returns a base64 string and explicitly sets a mime type, e.g.:
Describe the bug
Setting a mime type on a Ressource using FastMCP is being ignored by the low level server as the returned type is based on the ReadResourceRequest result type.
To Reproduce
Create any resource that returns a base64 string and explicitly sets a mime type, e.g.:
Invoke either directly or using the MCP inspector
Actual behavior
It returns
Note: a resource that it as bytes does not make much of a difference, it just changes the mime type to the very generic octet-stream.
Expected behavior
It should respect the mime type for both string and bytes content.
If you need a repo to reproduce it, I'm happy to help.
MCP version 1.2.0.
The text was updated successfully, but these errors were encountered: