Namespace Nexus\Mcp\Core\Schema

Optional annotations for the client. The client can use annotations to inform how objects are used or displayed.

Base interface for metadata with name (identifier) and title (display name) properties.

Capabilities a client may support. Known capabilities are defined here, in this schema, but this is not a closed set: any client can define its own, additional capabilities.

An opaque token used to represent a cursor for pagination.

An optionally-sized icon that can be displayed in a user interface.

Describes the MCP implementation.

The _meta extension slot carried by notifications and results.

Common params for any notification.

A progress token, used to associate progress notifications with the original request.

A revision of the Model Context Protocol identified by its release date.

A uniquely identifying ID for a request in JSON-RPC.

The _meta extension slot carried by request params. Adds a typed progressToken alongside open-ended extras.

Common params for any request.

Base for the result payload carried by a JSON-RPC success response. Concrete subclasses define the method-specific fields. This base only threads the typed _meta.

Represents a root directory or file that the server can operate on.

Capabilities that a server may support. Known capabilities are defined here, in this schema, but this is not a closed set: any server can define its own, additional capabilities.

Interface for classes that can be converted to and from arrays.

Marker for a content block that can be embedded in a prompt message or tool call result. Each variant carries its own type discriminator.

Base interface to add icons property.