Expand description
re-exports
Structs§
- Call
Tool Error - A specific error type that can hold any kind of error and is used to
encapsulate various error scenarios when a
CallToolRequest
fails. - Client
Jsonrpc Notification - “Similar to JsonrpcNotification , but with the variants restricted to client-side notifications.”
- Client
Jsonrpc Request - “Similar to JsonrpcRequest , but with the variants restricted to client-side requests.”
- Client
Jsonrpc Response - “Similar to JsonrpcResponse , but with the variants restricted to client-side responses.”
- SdkError
- Server
Jsonrpc Notification - “Similar to JsonrpcNotification , but with the variants restricted to server-side notifications.”
- Server
Jsonrpc Request - “Similar to JsonrpcRequest , but with the variants restricted to client-side requests.”
- Server
Jsonrpc Response - “Similar to JsonrpcResponse , but with the variants restricted to server-side responses.”
- Unknown
Tool - A custom error type
UnknownTool
that wraps aString
. This can be used as the error type in the result of aCallToolRequest
when a non-existent or unimplemented tool is called.
Enums§
- Client
Message - “Similar to JsonrpcMessage, but with the variants restricted to client-side messages.” ClientMessage represents a message sent by an MCP Client and received by an MCP Server.
- Message
From Client - An enum representing various types of messages that can be sent from an MCP Client.
It provides a typed structure for the message payload while skipping internal details like
requestId
and protocol version, which are used solely by the transport layer and do not need to be exposed to the user. - Message
From Server - An enum representing various types of messages that can be sent from an MCP Server.
It provides a typed structure for the message payload while skipping internal details like
requestId
and protocol version, which are used solely by the transport layer and do not need to be exposed to the user. - Message
Types - Notification
From Client - To determine standard and custom notifications received from the MCP Client Custom notifications are of type serde_json::Value and can be deserialized into any custom type.
- Notification
From Server - To determine standard and custom notifications received from the MCP Server Custom notifications are of type serde_json::Value and can be deserialized into any custom type.
- Request
From Client - To determine standard and custom request from the client side Custom requests are of type serde_json::Value and can be deserialized into any custom type.
- Request
From Server - To determine standard and custom request from the server side Custom requests are of type serde_json::Value and can be deserialized into any custom type.
- Result
From Client - To determine standard and custom results from the client side Custom results (CustomResult) are of type serde_json::Value and can be deserialized into any custom type.
- Result
From Server - To determine standard and custom results from the server side Custom results (CustomResult) are of type serde_json::Value and can be deserialized into any custom type.
- RpcError
Codes - Enum representing standard JSON-RPC error codes.
- SdkError
Codes - Enum representing SDK error codes.
- Server
Message - “Similar to JsonrpcMessage, but with the variants restricted to client-side messages.” ServerMessage represents a message sent by an MCP Server and received by an MCP Client.
Traits§
- From
Message - A trait for converting a message of type
T
intoSelf
. This is useful for transforming mcp messages into a Type that could be serialized into a JsonrpcMessage. - McpMessage
- RpcMessage
- Represents a generic MCP (Model Context Protocol) message. This trait defines methods to classify and extract information from messages.
- ToMessage
Type Aliases§
- MCPMessage
Deprecated - RPCMessage
Deprecated