Major issue -dependency on reactor, slf4j and netty

[hrstoyanov]

This project requires reactor (and therefore - netty), slf4j for reasons I cannot understand. In its current state it is more like "Spring MCP SDK" rather than "Java MCP SDK", so at least change the project title.

Java already has virtual threads and therefore, there is no need for any reactive frameworks. Also, since Java 9+ there is also a built-in logging facade System.Logger , so there is no need for slf4j either.

The use of jackson is also problematic - ideally there should be 2 modules - for jackson and standard jsonp.

Please clean it up.

[edburns]

Hello @hrstoyanov please consider this PR: #175 .

[hrstoyanov]

Changing the title is the proper way for this situation

[Aliaksie]

Hi! I created a PR that I hope will help with this!

[hrstoyanov]

@Aliaksie the proper way is to avoid any of the reactive frameworks, but use java virtual threads.

Likewise , remove slf4j and use java System.Logger facade

[Aliaksie]

hi @hrstoyanov, thank you for the feedback!

You're absolutely right about minimizing dependencies — and that’s exactly what my PR is structured to enable:

1. It introduces a clean mcp-spi module that is:

• Independent of Reactor, SLF4J, and Jackson
• Built on org.reactivestreams.Publisher only
• Supports pluggable codecs and logging via interfaces

2. mcp-reactor is now just one implementation. I keep Jackson and SLF4J as defaults there only to avoid breaking existing users but now it should be possible to provide own codecs and logging impl

This opens the door to a fully java-based module (i.e. mcp-java). I’d love to collaborate on that — but first, we need agreement on this decoupling PR .

cc @tzolov