Add README for the InMemoryTransport sample - #1769
Open
AkbarDizaji wants to merge 1 commit into
Open
Conversation
Documents the sample's purpose, how to run it, the expected output, and notes on the pipe wiring, following the style of the TasksExtension and WeatherAppServer sample READMEs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seven of the thirteen projects under
samples/have no README, includingInMemoryTransport, which is referenced from the Transports and Stateless concept docs via direct GitHub links — so readers land in the folder with no orientation.This adds a README for
InMemoryTransportfollowing the style of the existingTasksExtensionandWeatherAppServersample READMEs. It documents:McpServer.Createwithout a host/DI,StreamServerTransport/StreamClientTransportoverSystem.IO.Pipelinespipes, a delegate-based tool viaMcpServerTool.Create),dotnet runcommand and its actual output,server.RunAsync().Docs-only change; no code affected. READMEs for the remaining samples can follow as separate PRs if this shape looks right.
🤖 Generated with Claude Code