Skip to content

Fix compilation errors in README code samples #1369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeffhandley merged 1 commit into from
Feb 24, 2026
Merged

Fix compilation errors in README code samples #1369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ IList<McpClientTool> tools = await client.ListToolsAsync();
IChatClient chatClient = ...;
var response = await chatClient.GetResponseAsync(
"your prompt here",
new() { Tools = [.. tools] },
new() { Tools = [.. tools] });
```

## Getting Started (Server)
Expand Down Expand Up @@ -218,7 +218,7 @@ McpServerOptions options = new()

return ValueTask.FromResult(new CallToolResult
{
Content = [new TextContentBlock { Text = $"Echo: {message}", Type = "text" }]
Content = [new TextContentBlock { Text = $"Echo: {message}" }]
});
}

Expand Down
18 changes: 7 additions & 11 deletions src/ModelContextProtocol.Core/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ var result = await client.CallToolAsync(
cancellationToken: CancellationToken.None);

// echo always returns one and only one text content object
Console.WriteLine(result.Content.First(c => c.Type == "text").Text);
Console.WriteLine(result.Content.OfType<TextContentBlock>().First().Text);
```

Clients can connect to any MCP server, not just ones created using this library. The protocol is designed to be server-agnostic, so you can use this library to connect to any compliant server.
Expand All @@ -68,7 +68,7 @@ IList<McpClientTool> tools = await client.ListToolsAsync();
IChatClient chatClient = ...;
var response = await chatClient.GetResponseAsync(
"your prompt here",
new() { Tools = [.. tools] },
new() { Tools = [.. tools] });
```

## Getting Started (Server)
Expand All @@ -79,13 +79,9 @@ The core package provides the basic server functionality. Here's an example of c
using ModelContextProtocol.Server;
using System.ComponentModel;

// Create server options
var serverOptions = new McpServerOptions();

// Add tools directly
serverOptions.Capabilities.Tools = new()
// Create server options with tools
var serverOptions = new McpServerOptions
{
ListChanged = true,
ToolCollection = [
McpServerTool.Create((string message) => $"hello {message}", new()
{
Expand All @@ -96,9 +92,9 @@ serverOptions.Capabilities.Tools = new()
};

// Create and run server with stdio transport
var server = new McpServer(serverOptions);
using var stdioTransport = new StdioServerTransport();
await server.RunAsync(stdioTransport, CancellationToken.None);
await using var stdioTransport = new StdioServerTransport("EchoServer");
await using var server = McpServer.Create(stdioTransport, serverOptions);
await server.RunAsync(CancellationToken.None);
```

For more advanced scenarios with dependency injection, hosting, and automatic tool discovery, see the `ModelContextProtocol` package.
Loading