minor MCP ref docs improvements

Signed-off-by: Christian Tzolov <[email protected]>
Signed-off-by: 家娃 <[email protected]>

Author: tzolov

spring-ai-docs/src/main/antora/modules/ROOT/pages/api/mcp/mcp-annotations-client.adoc

@@ -37,23 +37,6 @@ public void handleLoggingWithParams(LoggingLevel level, String logger, String da
 }
 ----
 
-==== Client-Specific Handlers
-
-[source,java]
-----
-@McpLogging(clients = "server1")
-public void handleServer1Logs(LoggingMessageNotification notification) {
-    // Handle logs from specific server
-    logToFile("server1.log", notification);
-}
-
-@McpLogging(clients = "server2")
-public void handleServer2Logs(LoggingMessageNotification notification) {
-    // Handle logs from another server
-    logToDatabase("server2", notification);
-}
-----
-
 === @McpSampling
 
 The `@McpSampling` annotation handles sampling requests from MCP servers for LLM completions.
@@ -101,23 +84,6 @@ public class AsyncSamplingHandler {
 }
 ----
 
-==== Client-Specific Sampling
-
-[source,java]
-----
-@McpSampling(clients = "specialized-server")
-public CreateMessageResult handleSpecializedSampling(CreateMessageRequest request) {
-    // Use specialized model for this server
-    String response = generateSpecializedResponse(request);
-    
-    return CreateMessageResult.builder()
-        .role(Role.ASSISTANT)
-        .content(new TextContent(response))
-        .model("specialized-model")
-        .build();
-}
-----
-
 === @McpElicitation
 
 The `@McpElicitation` annotation handles elicitation requests to gather additional information from users.

spring-ai-docs/src/main/antora/modules/ROOT/pages/api/mcp/mcp-client-boot-starter-docs.adoc

@@ -24,15 +24,15 @@ The MCP Client Boot Starter provides:
 </dependency>
 ----
 
-The standard starter connects simultaneously to one or more MCP servers over `STDIO` (in-process), `SSE` and `Streamable Http` transports.
+The standard starter connects simultaneously to one or more MCP servers over `STDIO` (in-process), `SSE`, `Streamable Http` and `Stateless Streamable Http` transports.
 The SSE and Streamable-Http transports use the JDK HttpClient-based transport implementation.
 Each connection to an MCP server creates a new MCP client instance.
 You can choose either `SYNC` or `ASYNC` MCP clients (note: you cannot mix sync and async clients).
 For production deployment, we recommend using the WebFlux-based SSE & StreamableHttp connection with the `spring-ai-starter-mcp-client-webflux`.
 
 === WebFlux Client
 
-The WebFlux starter provides similar functionality to the standard starter but uses a WebFlux-based SSE and Streamable-Http transport implementation.
+The WebFlux starter provides similar functionality to the standard starter but uses a WebFlux-based Streamable-Http, Stateless Streamable-Http and SSE transport implementation.
 
 [source,xml]
 ----
@@ -179,27 +179,27 @@ The Claude Desktop format looks like this:
 }
 ----
 
-Currently, the Claude Desktop format supports only STDIO connection types.
+=== Streamable Http Transport Properties
 
-=== SSE Transport Properties
+Used for connecting to Streamable-HTTP and Stateless Streamable-HTTP MCP servers.
 
-Properties for Server-Sent Events (SSE) transport are prefixed with `spring.ai.mcp.client.sse`:
+Properties for Streamable Http transport are prefixed with `spring.ai.mcp.client.streamable-http`:
 
 [cols="3,4,3"]
 |===
 |Property |Description | Default Value
 
 |`connections`
-|Map of named SSE connection configurations
+|Map of named Streamable Http connection configurations
 |-
 
 |`connections.[name].url`
-|Base URL endpoint for SSE communication with the MCP server
+|Base URL endpoint for Streamable-Http communication with the MCP server
 |-
 
-|`connections.[name].sse-endpoint`
-|the sse endpoint (as url suffix) to use for the connection
-|`/sse`
+|`connections.[name].endpoint`
+|the streamable-http endpoint (as url suffix) to use for the connection
+|`/mcp`
 |===
 
 Example configuration:
@@ -209,34 +209,34 @@ spring:
   ai:
     mcp:
       client:
-        sse:
+        streamable-http:
           connections:
             server1:
               url: http://localhost:8080
             server2:
               url: http://otherserver:8081
-              sse-endpoint: /custom-sse
+              endpoint: /custom-sse
 ----
 
-=== Streamable Http Transport Properties
+=== SSE Transport Properties
 
-Properties for Streamable Http transport are prefixed with `spring.ai.mcp.client.streamable-http`:
+Properties for Server-Sent Events (SSE) transport are prefixed with `spring.ai.mcp.client.sse`:
 
 [cols="3,4,3"]
 |===
 |Property |Description | Default Value
 
 |`connections`
-|Map of named Streamable Http connection configurations
+|Map of named SSE connection configurations
 |-
 
 |`connections.[name].url`
-|Base URL endpoint for Streamable-Http communication with the MCP server
+|Base URL endpoint for SSE communication with the MCP server
 |-
 
-|`connections.[name].endpoint`
-|the streamable-http endpoint (as url suffix) to use for the connection
-|`/mcp`
+|`connections.[name].sse-endpoint`
+|the sse endpoint (as url suffix) to use for the connection
+|`/sse`
 |===
 
 Example configuration:
@@ -246,13 +246,13 @@ spring:
   ai:
     mcp:
       client:
-        streamable-http:
+        sse:
           connections:
             server1:
               url: http://localhost:8080
             server2:
               url: http://otherserver:8081
-              endpoint: /custom-sse
+              sse-endpoint: /custom-sse
 ----
 
 
@@ -284,10 +284,13 @@ Servers can request the list of roots from supporting clients and receive notifi
   - Resources change notifications - when the list of available server resources changes.
   - Prompts change notifications - when the list of available server prompts changes.
   - link:https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/logging[*Logging Handlers*] - standardized way for servers to send structured log messages to clients. 
-  
+  - link:https://modelcontextprotocol.io/specification/2025-06-18/basic/utilities/progress[*Progress Handlers*] - standardized way for servers to send structured progress messages to clients. 
+
 Clients can control logging verbosity by setting minimum log levels
 
 
+==== Client Customization Example
+
 You can implement either `McpSyncClientCustomizer` for synchronous clients or `McpAsyncClientCustomizer` for asynchronous clients, depending on your application's needs.
 
 [tabs]

spring-ai-docs/src/main/antora/modules/ROOT/pages/api/mcp/mcp-overview.adoc

@@ -10,7 +10,7 @@ Bootstrap your AI applications with MCP support using link:https://start.spring.
 
 == MCP Java SDK Architecture
 
-TIP: This section provides an overview for the link:https://modelcontextprotocol.io/sdk/java[MCP Java SDK architecture]. 
+TIP: This section provides an overview for the link:https://modelcontextprotocol.io/sdk/java/mcp-overview[MCP Java SDK architecture]. 
 For the Spring AI MCP integration, refer to the xref:#_spring_ai_mcp_integration[Spring AI MCP Boot Starters] documentation.
 
 The Java MCP implementation follows a three-layer architecture:
@@ -60,10 +60,7 @@ a| The MCP Server is a foundational component in the Model Context Protocol (MCP
 * Concurrent client connection management
 * Synchronous and Asynchronous API support
 * Transport implementations:
-** Stdio-based transport for process-based communication
-** Servlet-based SSE and Streamable-HTTP server transports
-** WebFlux SSE and Streamable-HTTP server transports for reactive HTTP streaming
-** WebMVC SSE and Streamable-HTTP server transports for servlet-based HTTP streaming
+** Stdio, Streamable-HTTP, Stateless Streamable-HTTP, SSE
 
 ^a| image::mcp/java-mcp-server-architecture.jpg[Java MCP Server Architecture, width=600]
 |===
@@ -77,8 +74,8 @@ Spring AI provides MCP integration through the following Spring Boot starters:
 
 === link:mcp-client-boot-starter-docs.html[Client Starters]
 
-* `spring-ai-starter-mcp-client` - Core starter providing `STDIO` and HTTP-based `SSE` and `Streamable-HTTP` support
-* `spring-ai-starter-mcp-client-webflux` - WebFlux-based `SSE` and `Streamable-HTTP` transport implementation
+* `spring-ai-starter-mcp-client` - Core starter providing `STDIO`, Servlet-based `Streamable-HTTP`, `Stateless Streamable-HTTP` and `SSE` support
+* `spring-ai-starter-mcp-client-webflux` - WebFlux-based  `Streamable-HTTP`, `Stateless Streamable-HTTP` and `SSE` transport implementation
 
 === link:mcp-server-boot-starter-docs.html[Server Starters]