modelcontextprotocol/ruby-sdk
Watch
1
0
Fork
You've already forked ruby-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #515 from koic/add_list_changed_notification_examples

Browse source 
[Doc] Add prompts/resources list-changed notification examples to README.md
This commit is contained in:
Koichi ITO 2026-08-15 00:11:19 +09:00 • committed by GitHub
commit ab17d50288
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -2226,6 +2226,18 @@ transport = MCP::Server::Transports::StreamableHTTPTransport.new(server)
# When tools change, notify clients # When tools change, notify clients
server.define_tool(name: "new_tool") { |**args| { result: "ok" } } server.define_tool(name: "new_tool") { |**args| { result: "ok" } }
server.notify_tools_list_changed server.notify_tools_list_changed
# When prompts change, notify clients
server.define_prompt(name: "new_prompt") do |args, server_context:|
MCP::Prompt::Result.new(messages: [])
end
server.notify_prompts_list_changed
# When resources change, notify clients
server.define_resource(uri: "resource://new", name: "new_resource", mime_type: "text/plain") do
[MCP::Resource::TextContents.new(uri: "resource://new", mime_type: "text/plain", text: "contents")]
end
server.notify_resources_list_changed
``` ```
You can use Stateless Streamable HTTP, where notifications are not supported and all calls are request/response interactions. You can use Stateless Streamable HTTP, where notifications are not supported and all calls are request/response interactions.