modelcontextprotocol/docs
Watch
1
0
Fork
You've already forked docs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(java): clarify core vs optional transport implementations

Browse source 
- Emphasize that core mcp module includes default STDIO and SSE transport implementations
- Clarify that default implementations don't require external web frameworks
- Mark Spring-specific transport implementations as optional dependencies

Signed-off-by: Christian Tzolov <christian.tzolov@broadcom.com>
This commit is contained in:
Christian Tzolov 2025-03-30 10:06:19 +02:00 • committed by Christian Tzolov
commit dc8cbf6431
1 changed files with 28 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

7
sdk/java/mcp-client.mdx
View file

@ -15,9 +15,10 @@ The MCP Client is a key component in the Model Context Protocol (MCP) architectu
- Prompt system interactions
- Optional features like roots management and sampling support
<Tip>
The [Spring-AI MCP Client](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) integration extends the MCP Java SDK to
provide auto-configuration for MCP client functionality in Spring Boot applications and integrating with Spring AI’s [tool execution framework](https://docs.spring.io/spring-ai/reference/api/tools.html).
<Tip>
The core `io.modelcontextprotocol.sdk:mcp` module provides STDIO and SSE client transport implementations without requiring external web frameworks.
Spring-specific transport implementations are available as an **optional** dependency `io.modelcontextprotocol.sdk:mcp-spring-webflux` for [Spring Framework](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) users.
</Tip>
The client provides both synchronous and asynchronous APIs for flexibility in different application contexts.