Hi all, today I took the liberty to have a look at the new mcp server and was quite surprized to see it just being 3 files of python. Haiving a deeper look at it, it seems to be a rather trivial server component, that simply translates MCP requests to Session API requests.
First of all … is it worth maintaining another repo for this? This way it requires a separate vote and release process, if we want ot release it. Also do I think that integrating an MCP server to the DataNode should be a lot more performant, than having a proxy server in between. I know the fastMCP tool isn’t available, however I don’t think that the MCP protocol is particularly complex. At least it doesn’t look as if we’re using any oft he higher level features in the current MCP server. Wouldn’t this just be 3 or 4 rest endpoints to consume JSON? Chris
