LeaveRequestMcpClientServer

This MCP server is the LeaveRequestMcpClientServer, a component that works with the MCP Client to handle leave-request related conversations and flows via a semantic kernel-enabled backend. The server leverages the OpenAI integration and MCP tooling to parse user intent, route prompts, and invoke actions defined by the MCP framework. To use it, start the MCP Server process (dotnet run --project McpServer/McpServer.csproj) and run the MCP Client (dotnet run --project McpClientApp.csproj) to begin an interactive session. The client communicates with the server to process messages, maintain context, and perform task-oriented interactions such as requesting leave, checking policy information, or generating appropriate responses through the integrated AI tooling.

Prerequisites:

• .NET 8.0 SDK installed
• Access to the repository with both McpServer and McpClientApp projects

Installation steps:

1. Open a terminal in the repository root.
2. Restore and build client dependencies: dotnet restore dotnet build
3. Build or run the MCP server and client as described below.

Running the MCP server and client:

• Start the MCP Server (leave-request server): dotnet run --project McpServer/McpServer.csproj (This runs the LeaveRequestMcpClientServer backend that the client will connect to.)
• Start the MCP Client: dotnet run --project McpClientApp/McpClientApp.csproj (This launches the Chat Console Client that interacts with the server.)

Tips and common issues:

• Ensure appsettings.json in the client contains a valid OpenAI API key and the intended model ID.
• The MCP Server executable path must be correctly configured when launching from the client, and the server must be running before the client connects.
• If you change models or endpoints in appsettings.json, restart both the server and client to apply changes.
• This setup uses .NET 8.0; make sure your environment variables and PATH include the dotnet CLI.
• If you encounter connection issues, verify network access between the client and server paths and confirm that the server process is up.