modelcontextprotocol/ruby-sdk
Watch
1
0
Fork
You've already forked ruby-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ruby-sdk/docs/_server/index.md
Koichi ITO c9d36b04bf [Doc] Align the Docs Page Names With the MCP Specification 
Three pages carried names the 2026-07-28 specification does not use: "Multi-Round-Trip Results" for
the pattern the specification titles Multi Round-Trip Requests (MRTR) and serves at basic/patterns/mrtr -
the results are the `InputRequiredResult` wire type, not the feature - plus "Completions" for the utility
the specification titles Completion, and "Notification Subscriptions" for the pattern it titles Subscriptions.
Retitle the three pages to the specification's names, move them to /server/mrtr/ and /client/mrtr/,
/server/completion/, and /server/subscriptions/ following the specification's slugs, update every internal reference,
and keep the URLs published with v1.3.0 working via jekyll-redirect-from.
The Discovery page keeps its title but moves from /server/discovery/ to /server/discover/, matching
the specification's slug and the `server/discover` RPC, with its published URL redirected the same way.
2026-08-22 18:07:38 +09:00

2.8 KiB
Raw Blame History

layout title nav_order permalink redirect_from
default Overview 1 /server/
/building-servers.html
/building-servers/

Building an MCP Server

The MCP::Server class is the core component that handles JSON-RPC requests and responses. It implements the Model Context Protocol specification, handling model context requests and responses.

Key Features

  • Implements JSON-RPC 2.0 message handling
  • Supports protocol initialization and capability negotiation
  • Manages tool registration and invocation
  • Supports prompt registration and execution
  • Supports resource registration and retrieval
  • Supports stdio and Streamable HTTP (including SSE) transports
  • Supports notifications for list changes (tools, prompts, resources)
  • Supports roots (server-to-client filesystem boundary queries)
  • Supports sampling (server-to-client LLM completion requests)
  • Supports cursor-based pagination for list operations
  • Supports cancellation of in-flight requests on both server and client (notifications/cancelled)

Supported Methods

  • initialize - Initializes the protocol and returns server capabilities
  • server/discover - Sessionless capability discovery (MCP 2026-07-28, SEP-2575): returns the server's capabilities before initialize and without an Mcp-Session-Id, and anchors the stateless modern lifecycle; see Discovery
  • subscriptions/listen - Long-lived notification subscription stream (MCP 2026-07-28, SEP-2575), replacing the legacy HTTP GET listening stream; see Subscriptions
  • Multi round-trip input_required results (MCP 2026-07-28, SEP-2322): handlers return MCP::Server::InputRequiredResult to ask the client for additional input instead of performing a server-initiated request; see Multi Round-Trip Requests
  • ping - Simple health check
  • logging/setLevel - Configures the minimum log level for the server
  • tools/list - Lists all registered tools and their schemas
  • tools/call - Invokes a specific tool with provided arguments
  • prompts/list - Lists all registered prompts and their schemas
  • prompts/get - Retrieves a specific prompt by name
  • resources/list - Lists all registered resources and their schemas
  • resources/read - Retrieves a specific resource by name
  • resources/templates/list - Lists all registered resource templates and their schemas
  • resources/subscribe - Subscribes to updates for a specific resource
  • resources/unsubscribe - Unsubscribes from updates for a specific resource
  • completion/complete - Returns autocompletion suggestions for prompt arguments and resource URIs
  • roots/list - Requests filesystem roots from the client (server-to-client)
  • sampling/createMessage - Requests LLM completion from the client (server-to-client)
  • elicitation/create - Requests user input from the client (server-to-client)