modelcontextprotocol
MCP server require more and clearer data packaging types to support different business scenarios in a more user-friendly manner
Is your feature request related to a problem? Please describe. I think the MCP server can clearly know what type of data response any function will return, such as any file, a large text data (from a database or elsewhere), and so on. The client only needs to determine the response type of the packaging, without verifying the data format. I think this is helpful for users to integrate MCP client into their system.
Describe the solution you'd like I tried to submit a PR, but it was rejected. I accept the reason for rejection, although I still don't quite understand why it was rejected. If someone could have a better implementation method, or if someone could tell me how to better implement the above scenario, I would greatly appreciate it
I believe that both the server and client follow predefined response types to make it easier for users' MCP clients to integrate different MCP servers without having to adapt to different MCP servers
The PR in question was attempting to add a new file content type - that's a change to the core protocol and would need a modification to the spec rather than just the SDK (in order to ensure compliance and compatibility with SDKs, clients, and servers built on top of these SDKs).
https://github.com/modelcontextprotocol/python-sdk/pull/811
See https://modelcontextprotocol.io/community/sep-guidelines#what-is-a-sep for information on SEPs
