All Classes and Interfaces
Class
Description
Utility class providing assertion methods for parameter validation.
Default implementation of the UriTemplateUtils interface.
A Server-Sent Events (SSE) client implementation using Java's Flow API for reactive
stream processing.
Record class representing a Server-Sent Event with its standard fields.
Interface for handling SSE events and errors.
Server-Sent Events (SSE) implementation of the
McpTransport that follows the MCP HTTP with SSE
transport specification, using Java's HttpClient.Builder for
HttpClientSseClientTransport.A Servlet-based implementation of the MCP HTTP with Server-Sent Events (SSE) transport
specification.
Builder for creating instances of HttpServletSseServerTransportProvider.
The Model Context Protocol (MCP) client implementation that provides asynchronous
communication with MCP servers using Project Reactor's Mono and Flux types.
The Model Context Protocol (MCP) server implementation that provides asynchronous
communication using Project Reactor's Mono and Flux types.
Represents an asynchronous exchange with a Model Context Protocol (MCP) client.
Factory class for creating Model Context Protocol (MCP) clients.
Asynchronous client specification.
Synchronous client specification.
Default implementation of the MCP (Model Context Protocol) session that manages
bidirectional JSON-RPC communication between clients and servers.
Functional interface for handling incoming JSON-RPC notifications.
Functional interface for handling incoming JSON-RPC requests.
Marker interface for the client-side MCP transport.
Based on the JSON-RPC 2.0
specification and the Model
Context Protocol Schema.
Base for objects that include optional annotations for the client.
Optional annotations for the client.
Binary contents of a resource.
Used by the client to call a tool provided by the server.
The server's response to a tools/call request from the client.
Builder for
McpSchema.CallToolResult.Clients can implement additional features to enrich connected MCP servers with
additional capabilities.
Roots define the boundaries of where servers can operate within the filesystem,
allowing them to understand which directories and files they have access to.
Provides a standardized way for servers to request LLM
sampling ("completions" or "generations") from language
models via clients.
Standard error codes used in MCP JSON-RPC responses.
Used by the client to get a prompt provided by the server.
The server's response to a prompts/get request from the client.
The server's response to a prompts/list request from the client.
The client's response to a roots/list request from the server.
The server's response to a tools/list request from the client.
The Model Context Protocol (MCP) provides a standardized way for servers to send
structured log messages to clients.
A prompt or prompt template that the server offers.
Describes an argument that a prompt can accept.
Describes a message returned as part of a prompt.
A known resource that the server is capable of reading.
The contents of a specific resource or sub-resource.
Resource templates allow servers to expose parameterized resources using URI
templates.
Represents a root directory or file that the server can operate on.
Sent from the client to request resources/updated notifications from the server
whenever a particular resource changes.
Text contents of a resource.
Represents a tool that the server provides.
Factory class for creating Model Context Protocol (MCP) servers.
Asynchronous server specification.
Synchronous server specification.
MCP server features specification that a particular server can choose to support.
Specification of a completion handler function with asynchronous execution support.
Specification of a prompt template with its asynchronous handler function.
Specification of a resource with its asynchronous handler function.
Specification of a tool with its asynchronous handler function.
Specification of a completion handler function with synchronous execution support.
Specification of a prompt template with its synchronous handler function.
Specification of a resource with its synchronous handler function.
Specification of a tool with its synchronous handler function.
Represents a Model Control Protocol (MCP) session on the server side.
Factory for creating server sessions which delegate to a provided 1:1 transport
with a connected client.
Notification handler for the initialization notification from the client.
Request handler for the initialization request.
A handler for client-initiated notifications.
A handler for client-initiated requests.
Marker interface for the server-side MCP transport.
The core building block providing the server-side MCP transport.
Represents a Model Control Protocol (MCP) session that handles communication between
clients and the server.
A synchronous client implementation for the Model Context Protocol (MCP) that wraps an
McpAsyncClient to provide blocking operations.A synchronous implementation of the Model Context Protocol (MCP) server that wraps
McpAsyncServer to provide blocking operations.Represents a synchronous exchange with a Model Context Protocol (MCP) client.
Defines the asynchronous transport layer for the Model Context Protocol (MCP).
Interface for working with URI templates.
Factory interface for creating instances of
McpUriTemplateManager.Server parameters for stdio client.
Implementation of the MCP Stdio transport that communicates with a server process using
standard input/output streams.
Implementation of the MCP Stdio transport provider for servers that communicates using
standard input/output streams.
Miscellaneous utility methods.