methods that are in a referenced library, you can manually register them by calling `MCPServer.Register();` with `T` being the class containing the desired methods. If your methods are marked with Semantic Kernel attributes, this will work as well. If the client supports list changed notifications, it will be notified when additional tools are registered. ## Advanced Usage ### Dynamic Tool Registration Register tools dynamically with custom implementation: ```csharp MCPServer.AddToolHandler(new Tool() { Name = "dynamicTool", Description = "A dynamic tool", InputSchema = new InputSchema { Type = "object", Required = ["input"], Properties = new Dictionary{ {"input", new ParameterSchema{Type="string", Description="Input value"}} } } }, (string input) => { return $"You provided: {input}"; }); ``` ### Use with Microsoft.Extensions.AI ```csharp // Client-side integration MCPClient client = new("AIClient", "1.0", "path/to/mcp/server"); IList functions = await client.GetFunctionsAsync(); ``` This list can be plugged into the [ChatOptions.Tools](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai.chatoptions?view=net-9.0-pp) property for an [IChatClient](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai.ichatclient?view=net-9.0-pp), Allowing MCP servers to be used seamlessly with Any IChatClient Implementation. ### Semantic Kernel Integration ```csharp using Microsoft.SemanticKernel; public class MySkillClass { [KernelFunction("MyFunction")] [Description("Description of my function")] public string MyFunction(string input) => $"Processed: {input}"; } // Register with MCPServer MCPServer.Register(); ``` Currently, This is the only way to make a Semantic kernel method registerable with the MCP server. If you have a use case that is not covered here, please reach out! ## API Reference ### Attributes - `[McpTool]` - Marks a class or method as an MCP tool - Optional parameters: - `Name` - The tool name (default: class/method name) - `Description` - Description of the tool - `[McpParameter]` - Provides metadata for function parameters - Optional parameters: - `Description` - Parameter description - `Required` - Whether the parameter is required (default: false) - `[McpResource]` - Marks a property or method as an MCP resource - Parameters: - `Name` - Resource name - `Uri` - Resource URI (can include templates) - `MimeType` - MIME type of the resource - `Description` - Resource description ### Server Methods - `MCPServer.StartAsync(string serverName, string version)` - Starts the MCP server - `MCPServer.Register()` - Registers a class containing tools or resources - `MCPServer.AddToolHandler(Tool tool, Delegate func)` - Registers a dynamic tool ### Client Methods - `new MCPClient(string name, string version, string server, string args = null, IDictionary env = null)` - Create a client instance - `client.GetToolsAsync()` - Get available tools - `client.CallToolAsync(string name, Dictionary parameters)` - Call a tool - `client.GetResourcesAsync()` - Get available resources - `client.GetFunctionsAsync()` - Get tools as AIFunctions ## XML Documentation Support MCPSharp automatically extracts documentation from XML comments: ```csharp ///

/// Provides mathematical operations ///

public class Calculator { ///

/// Adds two numbers together ///

/// The first number to add /// The second number to add /// The sum of the two numbers [McpTool] public static int Add( [McpParameter(true)] int a, [McpParameter(true)] int b) { return a + b; } } ``` Enable XML documentation in your project file: ```xml true

#dotnet-standard

MCPSharp

🚀 MCP Client-Server Repository