MarketPricesMCP

MarketPricesMCP is a .NET 8.0 MCP server that compares grocery product prices across Turkish markets in real time. It exposes MCP context types such as Title, Brand, Price, and Market, enabling MCP-compatible clients to request price comparisons for a given product. To use it with MCP clients like Claude or Cursor, you run the server as a local process and connect via an MCP configuration that points to the dotnet project. The server will listen for MCP requests and return structured context data representing product information, brand details, price amounts, and the markets where prices were found.

Using integration examples, you can wire the server into Claude by adding an MCP server entry that runs the project with dotnet run and points to the MarketPricesMCP.csproj. Cursor integration follows the same pattern: configure a local command-based MCP server that executes the same dotnet run command. Once connected, you can query by product name in Turkish (e.g., salatalık, domates, süt), and the server will search major Turkish markets and return the best-price results along with contextual metadata such as Title, Brand, Price, and Market.

Prerequisites:

• Git
• .NET 8.0 SDK/Runtime
• Access to internet to restore packages

Installation steps:

1. Clone the repository git clone https://github.com/Eneswunbeaten/MarketPricesMCP.git cd MarketPricesMCP
2. Restore and build dotnet restore dotnet build
3. Run the MCP server dotnet run --project "MarketPricesMCP/MarketPricesMCP/MarketPricesMCP.csproj" --no-build Note: If you use the MCP integration config, ensure the path in PATH_TO_YOUR_PROJECT matches your local project path.

Optional: Verify the server is running by connecting a MCP client (Claude, Cursor) with the provided configuration.

Tips and considerations:

• The MCP server is implemented in .NET 8.0 and uses the ModelContextProtocol for data context management.
• When integrating with clients, use the exact dotnet run command shown in the README; adjust PATH_TO_YOUR_PROJECT to your local path.
• If you encounter connection issues in clients, confirm that the server is running, the path to the csproj is correct, and that the required .NET runtime is installed.
• You can set environment variables like DOTNET_ENVIRONMENT and ASPNETCORE_URLS to tune runtime behavior; adapt as needed for your deployment environment.
• Ensure the MCP client’s request format aligns with the server’s context types: Title, Brand, Price, and Market.