Internal http.Server access in SSE mode

[earwin]

It would be very useful to have access to internal http.Server, and/or a capability to provide your own at initialization time.

There's a gazillion settings (e.g. around timeouts and TLS, but not limited to that) that would be awkward to re-expose in your API.
There's also a gazillion useful middlewares for query logging, tracing (think OTEL), access control and whatnot.
All of that is unreachable at the moment.

[ezynda3]

Could you give some pseudo code for how you would like to access this?

[earwin]

I'm not sure I would be able to keep it "pseudo". The moment you define a nice API, it's already mostly implemented 😸

If we forget about server-initiated notifications for a second, the most flexible way would be to expose server.SSEServer as http.Handler and leave the rest in your hands ("be a library, not a framework" paradigm);
Plus some sugar over it for cases where you don't want to bother with your http.Server settings (basically, the way it is done now).
... A cursory glance says there's nothing special about notifications.

I will probably, maybe, do a pull request.

[ezynda3]

Would this PR suit your use case? #29

[earwin]

Works for me, I think, thanks!

Note that the mux is reimplemented three times in one file now:
https://github.com/mark3labs/mcp-go/blob/main/server/sse.go#L48
https://github.com/mark3labs/mcp-go/blob/main/server/sse.go#L66
https://github.com/mark3labs/mcp-go/blob/main/server/sse.go#L278

I think the first two can just use server.SSEServer as a proper http.Handler now.

[ezynda3]

Thanks. Deduped.