Creates a Servlet-based `SSE`, `Streamable-HTTP`, and `Stateless` server transport.
It can be used with any Servlet container.
```java theme={null}
@Configuration
@EnableWebMvc
public class McpServerConfig implements WebMvcConfigurer {
@Bean
public HttpServletStreamableServerTransportProvider servletStreamableMcpSessionTransport() {
return HttpServletStreamableServerTransportProvider.builder()
.objectMapper(new ObjectMapper())
.contextExtractor(TEST_CONTEXT_EXTRACTOR)
.mcpEndpoint(MESSAGE_ENDPOINT)
.keepAliveInterval(Duration.ofSeconds(1))
.build();
}
//(Optionally) To use it with a Spring Web application, you can register it as a Servlet bean
@Bean
public ServletRegistrationBean customServletBean(HttpServletStreamableServerTransportProvider transportProvider) {
return new ServletRegistrationBean(transportProvider);
}
}
```
Implements the Streamable HTTP transport specification using the traditional Servlet API, providing:
- Bidirectional communication through Streamable-HTTP
- Asynchronous message handling using Servlet 6.0 async support
- Session management for multiple client connections
-
One endpoint:
- Message endpoint (configurable) for client-to-server requests
- Error handling and response formatting
- Graceful shutdown support
Current implementation lacks resumability due to lack of session storage
In distributed environments with multiple MCP Server instances, proper message routing is required.
To achieve scalability without significant infrastructure overhead consider the `Stateless Streamable-HTTP` server transport implementation.
Stateless MCP servers are designed for simplified deployments where session state is not maintained between requests.
They implement a subset of `Streamable-HTTP` specification that return `application/json` responses.
They are called stateless because unlike the standard Streamable-HTTP transport, they do not maintain session state between requests.
These servers are ideal for microservices architectures and cloud-native deployments.
```java theme={null}
@Configuration
@EnableWebMvc
public class McpServerConfig implements WebMvcConfigurer {
@Bean
public HttpServletStatelessServerTransport servletStatelessMcpSessionTransport() {
return HttpServletStatelessServerTransport.builder()
.objectMapper(new ObjectMapper())
.mcpEndpoint(MESSAGE_ENDPOINT)
.keepAliveInterval(Duration.ofSeconds(1))
.build();
}
//(Optionally) To use it with a Spring Web application, you can register it as a Servlet bean
@Bean
public ServletRegistrationBean customServletBean(HttpServletStatelessServerTransport transportProvider) {
return new ServletRegistrationBean(transportProvider);
}
@Bean
public McpStatelessSyncServer prepareSyncServerBuilder(HttpServletStatelessServerTransport statelessServerTransport) {
return McpServer.sync(statelessServerTransport)
.build();
}
}
}
```
Implements the Streamable-HTTP Stateless transport specification using the traditional Servlet API, providing:
- Unidirectional (client to server) communication through Streamable-HTTP
- Asynchronous message handling using Servlet 6.0 async support
- Session management for multiple client connections
-
One endpoint:
- Message endpoint (configurable) for client-to-server requests
- Error handling and response formatting
- Graceful shutdown support
Current implementation doesn't support sending Notifications back to the clients.
```java theme={null}
@Configuration
@EnableWebMvc
public class McpServerConfig implements WebMvcConfigurer {
@Bean
public HttpServletSseServerTransportProvider servletSseServerTransportProvider() {
return HttpServletSseServerTransportProvider.builder()
.objectMapper(new ObjectMapper())
.messageEndpoint("/mcp/message")
.keepAliveInterval(Duration.ofSeconds(1))
.build();
}
//(Optionally) To use it with a Spring Web application, you can register it as a Servlet bean
@Bean
public ServletRegistrationBean customServletBean(HttpServletSseServerTransportProvider transportProvider) {
return new ServletRegistrationBean(transportProvider);
}
}
```
Implements the MCP SSE transport specification using the traditional Servlet API, providing:
- Asynchronous message handling using Servlet 6.0 async support
- Session management for multiple client connections
-
Two types of endpoints:
- SSE endpoint (
/sse) for server-to-client events
- Message endpoint (configurable) for client-to-server requests
- Error handling and response formatting
- Graceful shutdown support