Struct Server 

pub struct Server { /* private fields */ }

A registered MCP server.

Registrations live in BTreeMaps so tools/list comes back in a stable order — an agent that re-reads the list should not see it shuffle.

Implementations

impl Server

pub fn new(name: impl Into<String>, version: impl Into<String>) -> Self

pub fn instructions(self, instructions: impl Into<String>) -> Self

Advice shown to the model once, at the start of a session.

pub fn tool(self, tool: Tool) -> Self

pub fn resource(self, resource: Resource) -> Self

pub fn prompt(self, prompt: Prompt) -> Self

pub fn name(&self) -> &str

pub fn tool_names(&self) -> Vec<&str>

pub fn capabilities(&self) -> Json

What this server advertises during the handshake.

Only the capabilities that are actually backed by a registration are announced: a client that sees tools and gets an empty list has been told something untrue.

pub async fn handle_text(&self, text: &str) -> Option<String>

Handle one complete transport frame, batches included.

None means there is nothing to send back — the frame held only notifications, which JSON-RPC answers with silence.

pub async fn handle_value(&self, value: &Json) -> Option<Json>

Handle one decoded message, returning the answer it deserves.

pub async fn dispatch( &self, method: &str, params: Json, ) -> Result<Json, RpcError>

Route one method to its handler.