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

8
sdk/java/mcp-server.mdx
View file

@ -21,11 +21,13 @@ The MCP Server is a foundational component in the Model Context Protocol (MCP) a
- Managing concurrent client connections
- Providing structured logging and notifications
<Tip>
The [Spring-AI MCP Server](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-starter-docs.html) integration extends the MCP Java SDK to
provide auto-configuration for MCP server functionality in Spring Boot applications.
<Tip>
The core `io.modelcontextprotocol.sdk:mcp` module provides STDIO and SSE server transport implementations without requiring external web frameworks.
Spring-specific transport implementations are available as an **optional** dependencies `io.modelcontextprotocol.sdk:mcp-spring-webflux`, `io.modelcontextprotocol.sdk:mcp-spring-webmvc` for [Spring Framework](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) users.
</Tip>
The server supports both synchronous and asynchronous APIs, allowing for flexible integration in different application contexts.
<Tabs>