Everything server

[aaronpowell]

This is an implementation of https://www.npmjs.com/package/@modelcontextprotocol/server-everything

The objective of this sample is to have all the usage covered using the .NET SDK and ensure that we can implement as much complexity as possible.

Improvements can be done with the completion of #70 and #72.

The only thing I think that is missing from here is logging - I can't find a way to set that. Logging implemented. I added a WithSetLoggingLevelHandler method to the McpServerBuilder and fixed the McpServerHandlers that wasn't exposing logging capabilities.

Commit history is a bit of a mess as I kept merging with branches as I was updating gaps.

[PederHP]

Is the intent to have this kept in sync with the reference everything server? If not, then I think a different name should be used to avoid confusion about the purpose and scope.

It looks (without having dived fully into it yet) to be equivalent right now, but I think it might be worth considering adding things not in the everything server and not necessarily committing to providing equivalent functionality as it evolves. On the other hand, there is a value to having a directly comparable server.

[aaronpowell]

I have done the logging stuff in the (integration test) TestServer to match what the everything server has. It was modified from 15 to 1 second frequency recently but that should be trivial to adjust.

Ah sweet, I must've missed that. I'll get it included.

Is the intent to have this kept in sync with the reference everything server? If not, then I think a different name should be used to avoid confusion about the purpose and scope.

It looks (without having dived fully into it yet) to be equivalent right now, but I think it might be worth considering adding things not in the everything server and not necessarily committing to providing equivalent functionality as it evolves. On the other hand, there is a value to having a directly comparable server.

My thought was to keep it in sync, as best as possible since a) it provides a good way to dogfood all the code paths and b) it's useful to have a direct comparison.

[aaronpowell]

@PederHP - Added logging in a similar design to TestServer.

Also added a new method to the McpServerBuilder so you can set it there (it's not super easy otherwise if you're using the builder pattern).

[halter73]

Thank you!