Get the FREE Ultimate OpenClaw Setup Guide →

eShopLite

eShopLite is a set of reference .NET applications implementing an eCommerce site with features like Semantic Search, MCP, Reasoning models and more.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio azure-samples-eshoplite dotnet run --project path/to/eshoplite/scenarios/06-mcp/McpServer/McpServer.csproj \
  --env MCP_PORT="Port for MCP server to listen on (e.g., 5000)" \
  --env MCP_LOG_LEVEL="Logging level (Information|Debug|Warning|Error)"

How to use

eShopLite includes a dedicated MCP server as part of its scenarios, demonstrating the Model Context Protocol machinery in a realistic eCommerce-like setting. The MCP server enables structured, context-rich interactions between an MCP client and server, including model reasoning, function calling, and event streaming via Server-Sent Events. Use this MCP implementation to explore multi-turn AI reasoning, passing fragmented context, and coordinating between vector stores and LLMs within the eShopLite ecosystem. Start the MCP server first, then connect an MCP client to exercise semantic and tool-using conversations, inspect the context sharing, and observe how model calls are orchestrated through the MCP endpoints.

How to install

Prerequisites:

  • .NET 9 SDK installed
  • Git
  • A compatible environment for running the eShopLite repository (Windows, macOS, or Linux)

Installation steps:

  1. Clone the repository:
git clone https://github.com/azure-samples/eshoplite.git
  1. Navigate to the MCP scenario folder:
cd eshoplite/scenarios/06-mcp
  1. Restore and run the MCP server project:
dotnet restore
dotnet run --project McpServer/McpServer.csproj
  1. Ensure prerequisites are running (e.g., any dependent vector stores or AI services) and note the port printed by the server for client connections.

Additional notes

  • The MCP server integrates with the eShopLite MCP client to demonstrate model-context-based reasoning.
  • If the server fails to bind to the default port, set MCP_PORT via environment variable or adjust the port in the project settings.
  • Common issues include mismatched API versions between client and server, and missing credentials for any external vector databases or AI services.
  • Environment variables you may encounter or adjust: MCP_PORT, MCP_LOG_LEVEL, VECTOR_DB_CONNECTION_STRING, OPENAI_API_KEY.
  • To test, use an MCP client wired to the same port and experiment with semantic prompts and function-calling flows as shown in the MCP scenario.

Related MCP Servers

Sponsor this space

Reach thousands of developers