LeaveRequestMcpServer

This MCP server implements two tools under the MCP framework: EchoTool and LeaveRequestTool. The server communicates using standard input/output (Stdio) and automatically registers its tools at startup. EchoTool provides a simple echo service with two operations: Echo, which returns the input message as-is, and Reverse, which returns the input string reversed. LeaveRequestTool offers HR-related functions: GetLeaveRecordAmount to query an employee's remaining leave days, LeaveRequest to submit a leave application and receive a result, and GetCurrentDate to fetch the current date. To interact with the server, run it locally (via dotnet run) and connect to its Stdio interface as described by the MCP protocol in your environment. You can invoke the tools through the MCP client tooling, which will discovery and execute the appropriate operations on each tool.

Prerequisites:

• .NET 8+ SDK installed
• Access to the repository containing MinimalMcpServer

Installation steps:

1. Clone the repository: git clone <repository-url>
2. Navigate to the project directory (containing MinimalMcpServer.csproj).
3. Restore dependencies: dotnet restore MinimalMcpServer.csproj
4. Build the project: dotnet build MinimalMcpServer.csproj
5. Run the MCP server: dotnet run --project MinimalMcpServer.csproj

Once running, the server will expose EchoTool and LeaveRequestTool via the MCP Stdio transport.

Notes and tips:

• The server relies on .NET 8+ and the Microsoft.Extensions.Hosting and ModelContextProtocol packages. Make sure your environment matches the required versions.
• Tools are registered automatically at startup; no manual registration is typically necessary.
• If you need to customize environment variables (for example, to configure logging, data stores, or external service endpoints), you can extend the hosting configuration in Program.cs or set environment variables prior to running.
• Ensure your MCP client is configured to communicate over Stdio if you’re testing locally; networked transports would require different configuration not shown in this example.
• If you modify MinimalMcpServer.csproj or the source, re-run dotnet build to ensure the server is up-to-date.