mcp servers dont log request payload size before processing... is this expected??
i tested @modelcontextprotocol/server-filesystem 1.0.1 and @modelcontextprotocol/server-sqlite 0.3.0 yesterday and neither logs the request payload size before processing.... this seems like it could cause issues when debugging large requests that timeout or fail. also the error messages dont include the payload size either so its hard to tell if the failure was because of size or something else.... am i missing something or is this just not implemented yet?
need this badly.... tried to debug slow mcp tool yesterday and had zero visibility into whether the slowness was network latency, tool execution time, or serialization overhead
need this badly. tried to debug why mcp tool was slow yesterday and had zero visibility into request size. ended up wrapping the sdk with custom logging that dumps content-length header but this should be in the sdk by default