904083c681* Base for Java docs * docs(java): Migrate Java-SDK/docs Add visual documentation for Java SDK architecture: - PlantUML class diagrams showing core components and relationships - Client and server architecture diagrams - Stack architecture overview - Generated UML class diagram with detailed implementation structure * Add Java Client and Server quickstarts * reorder, redact, correct java-sdk docs Signed-off-by: Dariusz Jędrzejczyk <dariusz.jedrzejczyk@broadcom.com> * updated updates.mdx * fix docs.json --------- Signed-off-by: Dariusz Jędrzejczyk <dariusz.jedrzejczyk@broadcom.com> Co-authored-by: Christian Tzolov <christian.tzolov@broadcom.com> Co-authored-by: Dariusz Jędrzejczyk <dariusz.jedrzejczyk@broadcom.com> Co-authored-by: David Soria Parra <davidsp@anthropic.com>
167 lines
6.8 KiB
Text
167 lines
6.8 KiB
Text
---
|
|
title: Overview
|
|
description: Introduction to the Model Context Protocol (MCP) Java SDK
|
|
---
|
|
|
|
Java SDK for the [Model Context Protocol](https://modelcontextprotocol.org/docs/concepts/architecture)
|
|
enables standardized integration between AI models and tools.
|
|
|
|
## Features
|
|
|
|
- MCP Client and MCP Server implementations
|
|
- Supports Synchronous and Asynchronous programming paradigms
|
|
- Standard MCP operations support:
|
|
- Protocol [version compatibility negotiation](https://spec.modelcontextprotocol.io/specification/2024-11-05/basic/lifecycle/#initialization)
|
|
- [Tool](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/tools/) discovery, execution, list change notifications
|
|
- [Resource](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/resources/) management with URI templates
|
|
- [Roots](https://spec.modelcontextprotocol.io/specification/2024-11-05/client/roots/) list management and notifications
|
|
- [Prompt](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/prompts/) handling and management
|
|
- [Sampling](https://spec.modelcontextprotocol.io/specification/2024-11-05/client/sampling/) support for AI model interactions
|
|
- Multiple transport implementations:
|
|
- Core transports:
|
|
- Stdio-based transport for process-based communication
|
|
- Java HttpClient-based SSE client transport for HTTP SSE Client-side streaming
|
|
- Servlet-based SSE server transport for HTTP SSE Server streaming
|
|
- Spring-based transports:
|
|
- WebFlux SSE transport for reactive HTTP streaming
|
|
- WebMVC SSE transport for servlet-based HTTP streaming
|
|
|
|
## Architecture
|
|
|
|
|
|
|
|
|
|
The SDK follows a layered architecture with clear separation of concerns:
|
|
|
|
- **Client/Server Layer (McpClient/McpServer)**: Both use McpSession for sync/async operations,
|
|
with McpClient handling client-side protocol operations and McpServer managing server-side protocol operations.
|
|
- **Session Layer (McpSession)**: Manages communication patterns and state using DefaultMcpSession implementation.
|
|
- **Transport Layer (McpTransport)**: Handles JSON-RPC message serialization/deserialization via:
|
|
- StdioTransport (stdin/stdout) in the core module
|
|
- HTTP SSE transports in dedicated transport modules (Java HttpClient, Spring WebFlux, Spring WebMVC)
|
|
|
|
|
|
|
|
The following class diagram illustrates the layered architecture of the MCP SDK, showing
|
|
the relationships between core interfaces (McpTransport, McpSession), their implementations,
|
|
and the client/server components. It highlights how the transport layer connects to sessions, which in turn support both synchronous and asynchronous client/server implementations.
|
|
|
|
|
|
|
|
Key Interactions:
|
|
|
|
- **Client/Server Initialization**: Transport setup, protocol compatibility check, capability negotiation, and implementation details exchange.
|
|
- **Message Flow**: JSON-RPC message handling with validation, type-safe response processing, and error handling.
|
|
- **Resource Management**: Resource discovery, URI template-based access, subscription system, and content retrieval.
|
|
|
|
## Dependencies
|
|
|
|
Add the following Maven dependency to your project:
|
|
|
|
<Tabs>
|
|
<Tab title="Maven">
|
|
The core MCP functionality:
|
|
|
|
```xml
|
|
<dependency>
|
|
<groupId>io.modelcontextprotocol.sdk</groupId>
|
|
<artifactId>mcp</artifactId>
|
|
</dependency>
|
|
```
|
|
|
|
For HTTP SSE transport implementations, add one of the following dependencies:
|
|
|
|
```xml
|
|
<!-- Spring WebFlux-based SSE client and server transport -->
|
|
<dependency>
|
|
<groupId>io.modelcontextprotocol.sdk</groupId>
|
|
<artifactId>mcp-spring-webflux</artifactId>
|
|
</dependency>
|
|
|
|
<!-- Spring WebMVC-based SSE server transport -->
|
|
<dependency>
|
|
<groupId>io.modelcontextprotocol.sdk</groupId>
|
|
<artifactId>mcp-spring-webmvc</artifactId>
|
|
</dependency>
|
|
```
|
|
</Tab>
|
|
<Tab title="Gradle">
|
|
The core MCP functionality:
|
|
|
|
```groovy
|
|
dependencies {
|
|
implementation platform("io.modelcontextprotocol.sdk:mcp")
|
|
//...
|
|
}
|
|
```
|
|
|
|
For HTTP SSE transport implementations, add one of the following dependencies:
|
|
|
|
```groovy
|
|
// Spring WebFlux-based SSE client and server transport
|
|
dependencies {
|
|
implementation platform("io.modelcontextprotocol.sdk:mcp-spring-webflux")
|
|
}
|
|
|
|
// Spring WebMVC-based SSE server transport
|
|
dependencies {
|
|
implementation platform("io.modelcontextprotocol.sdk:mcp-spring-webmvc")
|
|
}
|
|
```
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
### Bill of Materials (BOM)
|
|
|
|
The Bill of Materials (BOM) declares the recommended versions of all the dependencies used by a given release.
|
|
Using the BOM from your application's build script avoids the need for you to specify and maintain the dependency versions yourself.
|
|
Instead, the version of the BOM you're using determines the utilized dependency versions.
|
|
It also ensures that you're using supported and tested versions of the dependencies by default, unless you choose to override them.
|
|
|
|
Add the BOM to your project:
|
|
|
|
<Tabs>
|
|
<Tab title="Maven">
|
|
```xml
|
|
<dependencyManagement>
|
|
<dependencies>
|
|
<dependency>
|
|
<groupId>io.modelcontextprotocol.sdk</groupId>
|
|
<artifactId>mcp-bom</artifactId>
|
|
<version>0.7.0-SNAPSHOT</version>
|
|
<type>pom</type>
|
|
<scope>import</scope>
|
|
</dependency>
|
|
</dependencies>
|
|
</dependencyManagement>
|
|
```
|
|
</Tab>
|
|
|
|
<Tab title="Gradle">
|
|
```groovy
|
|
dependencies {
|
|
implementation platform("io.modelcontextprotocol.sdk:mcp-bom:0.7.0-SNAPSHOT")
|
|
//...
|
|
}
|
|
```
|
|
|
|
Gradle users can also use the Spring AI MCP BOM by leveraging Gradle (5.0+) native support for declaring dependency constraints using a Maven BOM.
|
|
This is implemented by adding a 'platform' dependency handler method to the dependencies section of your Gradle build script.
|
|
As shown in the snippet above this can then be followed by version-less declarations of the Starter Dependencies for the one or more spring-ai modules you wish to use, e.g. spring-ai-openai.
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
Replace the version number with the version of the BOM you want to use.
|
|
|
|
### Available Dependencies
|
|
|
|
The following dependencies are available and managed by the BOM:
|
|
|
|
- Core Dependencies
|
|
- `io.modelcontextprotocol.sdk:mcp` - Core MCP library providing the base functionality and APIs for Model Context Protocol implementation.
|
|
- Transport Dependencies
|
|
- `io.modelcontextprotocol.sdk:mcp-spring-webflux` - WebFlux-based Server-Sent Events (SSE) transport implementation for reactive applications.
|
|
- `io.modelcontextprotocol.sdk:mcp-spring-webmvc` - WebMVC-based Server-Sent Events (SSE) transport implementation for servlet-based applications.
|
|
- Testing Dependencies
|
|
- `io.modelcontextprotocol.sdk:mcp-test` - Testing utilities and support for MCP-based applications.
|
|
|