Overhaul tool handling (#89)
* Overhaul tool handling
- Renames [McpTool{Type}] to [McpServerTool{Type}], in order to distinguish representations of tools on the server from tools on the client.
- Enables [McpServerTool] methods to have arguments injected from DI, as well as a specific set of types from the implementation directly, like IMcpServer.
- Renames WithTools to WithToolsFromAssembly.
- All of the WithToolsXx methods now publish each individual McpServerTool into DI; other code can do so as well. The options setup code gathers all of the tools from DI and combines them into a collection which is then stored in McpServerOptions and used to construct the server.
- The server tools specified via DI as well as manually-provided handlers, using CallToolHandler as a fallback in case the requested tool doesn't exist in the tools collection, and ListToolsHandler augments the information for whatever tools exist.
- The tools are stored in McpServerOptions in a new McpServerToolCollection type, which is a thread-safe container that exposes add/removal notification. Adding/removing tools triggers a change notification that in turn sends a notification to the client about a tools update.
- The ServerOptions are exposed from the server instance.
- Removed cursor-based APIs from McpClientExtensions.
- Changed McpClientExtensions APIs to return `Task<IList<...>` rather than `IAsyncEnumerable<...>`.
I'm sure this will need to evolve further before we're "done", but it's a significant improvement from where we are now. One area I'm not super happy with is the notifying collection; that might work ok for a stdio server, where you can grab the created collection from the server's options and mutate it, but I don't know how well that's going to work for sse servers.
* Make McpServerTool{Collection} extensible
* Fix README.md example
* Add notifications test
* Address feedback
This commit is contained in:
parent
aafa9d929d
commit
caca2ae61d
1 changed files with 2703 additions and 686 deletions
|
|
@ -1,5 +1,4 @@
|
|||
using System.Reflection;
|
||||
using ModelContextProtocol.Protocol.Types;
|
||||
using ModelContextProtocol.Server;
|
||||
using Microsoft.Extensions.Options;
|
||||
using ModelContextProtocol.Utils;
|
||||
|
|
@ -7,30 +6,66 @@ using ModelContextProtocol.Utils;
|
|||
namespace ModelContextProtocol.Configuration;
|
||||
|
||||
/// <summary>
|
||||
/// Configures the McpServerOptions using provided server handlers.
|
||||
/// Configures the McpServerOptions using addition services from DI.
|
||||
/// </summary>
|
||||
/// <param name="serverHandlers">The server handlers configuration options.</param>
|
||||
internal sealed class McpServerOptionsSetup(IOptions<McpServerHandlers> serverHandlers) : IConfigureOptions<McpServerOptions>
|
||||
/// <param name="serverTools">Tools individually registered.</param>
|
||||
internal sealed class McpServerOptionsSetup(
|
||||
IOptions<McpServerHandlers> serverHandlers,
|
||||
IEnumerable<McpServerTool> serverTools) : IConfigureOptions<McpServerOptions>
|
||||
{
|
||||
/// <summary>
|
||||
/// Configures the given McpServerOptions instance by setting server information
|
||||
/// and applying custom server handlers.
|
||||
/// and applying custom server handlers and tools.
|
||||
/// </summary>
|
||||
/// <param name="options">The options instance to be configured.</param>
|
||||
public void Configure(McpServerOptions options)
|
||||
{
|
||||
Throw.IfNull(options);
|
||||
|
||||
var assemblyName = Assembly.GetEntryAssembly()?.GetName();
|
||||
|
||||
// Set server information based on the entry assembly
|
||||
options.ServerInfo = new Implementation
|
||||
// Configure the option's server information based on the current process,
|
||||
// if it otherwise lacks server information.
|
||||
var assemblyName = (Assembly.GetEntryAssembly() ?? Assembly.GetCallingAssembly()).GetName();
|
||||
if (options.ServerInfo is not { } serverInfo ||
|
||||
serverInfo.Name is null ||
|
||||
serverInfo.Version is null)
|
||||
{
|
||||
Name = assemblyName?.Name ?? "McpServer",
|
||||
Version = assemblyName?.Version?.ToString() ?? "1.0.0",
|
||||
};
|
||||
options.ServerInfo = options.ServerInfo is null ?
|
||||
new()
|
||||
{
|
||||
Name = assemblyName.Name ?? "McpServer",
|
||||
Version = assemblyName.Version?.ToString() ?? "1.0.0",
|
||||
} :
|
||||
options.ServerInfo with
|
||||
{
|
||||
Name = options.ServerInfo.Name ?? assemblyName.Name ?? "McpServer",
|
||||
Version = options.ServerInfo.Version ?? assemblyName.Version?.ToString() ?? "1.0.0",
|
||||
};
|
||||
}
|
||||
|
||||
// Apply custom server handlers
|
||||
// Collect all of the provided tools into a tools collection. If the options already has
|
||||
// a collection, add to it, otherwise create a new one. We want to maintain the identity
|
||||
// of an existing collection in case someone has provided their own derived type, wants
|
||||
// change notifications, etc.
|
||||
McpServerToolCollection toolsCollection = options.Capabilities?.Tools?.ToolCollection ?? [];
|
||||
foreach (var tool in serverTools)
|
||||
{
|
||||
toolsCollection.TryAdd(tool);
|
||||
}
|
||||
|
||||
if (!toolsCollection.IsEmpty)
|
||||
{
|
||||
options.Capabilities = options.Capabilities is null ?
|
||||
new() { Tools = new() { ToolCollection = toolsCollection } } :
|
||||
options.Capabilities with
|
||||
{
|
||||
Tools = options.Capabilities.Tools is null ?
|
||||
new() { ToolCollection = toolsCollection } :
|
||||
options.Capabilities.Tools with { ToolCollection = toolsCollection },
|
||||
};
|
||||
}
|
||||
|
||||
// Apply custom server handlers.
|
||||
serverHandlers.Value.OverwriteWithSetHandlers(options);
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue