examples/

A minimal MCP stdio server: one typed tool, one resource, one prompt.

A calculator MCP server showing typed tools: the input schema (with enum and required constraints) is inferred from the Go struct, arguments are validated against it before the handler runs, and the output schema is derived from the return type.

Elicitation via MRTR (multi round-trip requests), the 2026-07-28 replacement for server-initiated requests: the server answers tools/call with an input_required interim result; the client fulfills the input requests and retries automatically.

A file-serving MCP server: files in a directory are exposed as resources under file:/// URIs, with path traversal blocked by the SDK (filepath.Localize + os.OpenRoot).

Streamable HTTP demo: a server exposing MCP on a single POST endpoint, and a client mode that exercises it (discover, tool call with progress over SSE, and a live subscription stream).

The official tasks extension (io.modelcontextprotocol/tasks): a tool call becomes a durable task the client polls, including an input_required rendezvous answered via tasks/update.