eShopLite

MCP搜索检索

提供方 Azure-Samples

搜索检索 未标注 API Key 社区 / 第三方 CursorVS CodeCodexZed

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

一句话选型结论

按资料字段整理

eShopLite 属于搜索检索类 MCP 服务器,传输方式未标注,API Key,可直接接入 Cursor、VS Code、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

mcp embeddings semantic search aspire rag azd azure openai azd templates

支持客户端

适用场景

mcpembeddingssemantic search

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、VS Code、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、VS Code 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
eShopLite当前 未标注 未标注 未标注 无 未标注
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Azure-Samples上游标注的维护方 Azure-Samples
分类搜索检索本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · c#本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.9 KB
来自项目仓库与上游目录的原文,未做删改

eShopLite

eShopLite is a set of reference .NET applications implementing an eCommerce site with features like Semantic Search, Model Context Protocol (MCP), Reasoning models, vector databases, and more.

> - ☁️ Scenarios use .NET and Aspire, with a stable .NET 10 baseline and an isolated .NET 11 RC2 scenario for experimental Blazor AI components. See the dependency baseline below for compatibility exceptions.
> - 🌟 Don't forget to star (🌟) this repo to find it easier later.
> - ➡️ Get your own copy by Forking this repo and find it next in your own repositories.
> - ❓ Have a question? Besides creating issues or pull requests, the best option for questions is to join the Azure AI Discord channel, where a team of AI experts can help you.

Features

This project framework provides the following features:

  • Modern .NET application architecture with Aspire
  • Various search capabilities (keyword search, semantic search)
  • Integration with multiple AI models (GPT-4o, DeepSeek-R1, etc.)
  • Vector database implementations (In Memory, Azure AI Search, Chroma DB and others)
  • Real-time audio capabilities
  • Model Context Protocol (MCP) server and client implementation

eShopLite Scenarios

The project includes several scenarios demonstrating different capabilities:

Scenario Description Key Technologies
01 - Semantic Search A reference .NET application implementing an eCommerce site with Search features using Keyword Search and Semantic Search. Aspire, OpenAI GPT-4.1-mini, In-memory Vector DB
02 - Azure AI Search Implements an eCommerce site with Keyword Search using SQL queries and Semantic Search with Vector Database and Azure AI Search. Azure AI Search, OpenAI Embeddings, SQL Server
03 - Realtime Audio Extends the eCommerce site with advanced search features and real-time audio capabilities powered by the GPT-4o Realtime Audio API. GPT-4o Realtime Audio API, Audio in Blazor, Aspire
04 - Chroma DB Implements semantic search functionality using Chroma DB, an open-source database designed for AI applications. Chroma DB, OpenAI Embeddings, .NET SDK
05 - DeepSeek-R1 Demonstrates integration of the DeepSeek-R1 model for enhanced semantic understanding and search capabilities. DeepSeek-R1, Aspire, Vector Embeddings
06 - Model Context Protocol (MCP) Implements the Model Context Protocol (MCP) for advanced AI interactions with MCP Servers and MCP Clients. Model Context Protocol, Function Calling, SSE Events
07 - Agents Concurrent Demonstrates concurrent agent orchestration and advanced AI agent collaboration patterns. Aspire, Multi-Agent Systems, Orchestration
08 - SQL Server 2025 Demonstrates the use of vector search and vector indexes in the SQL Database Engine SQL Server 2025, Vector Search, Vector Indexes
09 - Azure App Service Shows how to deploy an Aspire multi-service eCommerce app to Azure App Service, using SQLite for data and integrating AI search. Azure App Service, Aspire, OpenAI, SQLite
10 - A2A Network Demonstrates advanced agent-to-agent (A2A) communication and orchestration patterns in Aspire, including multi-agent collaboration and reasoning. Aspire, Multi-Agent Systems, A2A Protocol
11 - GitHub Models Local-first AI development using GitHub Models during local runs, with automatic switch to Azure OpenAI when deployed. Aspire, GitHub Models, Azure OpenAI
12 - Azure Functions Optional Azure Functions façade for semantic search and an alternate deployment boundary for vector search. Azure Functions, Aspire, Azure OpenAI
13 - Observability Assistant with Foundry Local Summarizes logs, traces, and incidents with a local-first observability assistant. Aspire, OpenTelemetry, Foundry Local, Microsoft.Extensions.AI
14 - Product Discovery Copilot Turns search into natural-language product discovery with grounded explanations. Semantic search, vector search, Microsoft.Extensions.AI
15 - Store Intelligence Report Generates daily business and operational store intelligence reports. App data, telemetry, AI summarization, reports
16 - MCP Store Operations Tools Exposes safe store capabilities as MCP tools for agent use. MCP, Aspire, app APIs, tool calling
17 - A2A Store Operations Network Shows specialized agents collaborating around the store app through A2A. A2A, Microsoft Agent Framework, hosted agents
18 - Blazor Agentic UI Experimental streaming shopping assistant with catalog cards and human-approved cart actions. .NET 11 RC2, Blazor AI components, AG-UI, Microsoft Agent Framework, Aspire

New to Scenario 18? Start with its three-step quick start,
then explore the screenshots and
blog-to-code walkthrough.

Getting Started

Prerequisites

  • .NET 10 SDK 10.0.402, pinned in the root global.json
  • Docker Desktop or Podman
  • Azure Developer CLI (azd) (for Azure deployment)
  • Git
  • Aspire CLI: install with dotnet tool install -g Aspire.Cli --version 13.6.1 (used for setting local secrets via aspire secret set)

Dependency baseline

The October 14, 2026 refresh updates the 17 existing scenarios other than 14-MAFDevUI
to Aspire 13.6.1 and the latest compatible NuGet releases. The root SDK stays on stable
.NET 10; Scenario 18 overrides it with .NET 11 RC2
for the experimental Blazor components. Install both SDKs to work on all scenarios.

The refresh includes Microsoft.Extensions.AI 10.11.0, OpenTelemetry 1.19,
Microsoft Agent Framework 1.24.0, MCP 2.2.0, and A2A 1.0.0-preview3 where used.
Existing prerelease dependencies remain prerelease where no stable replacement provides
the required functionality. MCP SSE transports and A2A text parts have been migrated to
the current APIs rather than merely changing package versions.

Scenarios 08 and 12 deliberately retain the latest EF Core 9 servicing release, 9.0.21:
their EFCore.SqlServer.VectorSearch 9.0.0 provider requires that EF major. The other
EF-backed scenarios use 10.0.13. Local dotnet-ef tool manifests follow the matching
EF major. Upgrading the SQL vector provider to native EF 10 requires a separate vector
entity/query migration, not mixing EF 9 relational assemblies with EF 10 tests.
Direct PKCS references select patched 10.0.13 instead of vulnerable transitive versions.

The MAFDevUI scenario subsequently completed its
compatible dependency and API migration after the Azure MCP prerequisite was supplied.
Its build and 27 tests pass, including offline DevUI/Responses integration coverage.
Live validation with both Azure CLI identity and the updated saved API key passed
embeddings, stock tools, streaming workflows, and all three checkout tiers.
Identity-mode orchestrator checks also confirmed no fallback.
Optional Foundry-hosted agents remain unverified. Builds and
existing tests passed for
the other 17 existing scenario solutions (80 existing tests), and Scenario 18 has 29
passing tests. Scenario 18 was also validated locally with SQL Server 2025, real Foundry
embeddings, and gpt-6-luna via Responses: streamed catalog cards, cart rejection/approval,
missing product specifications, and restart against existing data. These checks do not
establish cloud deployability or validate every other scenario against real models.

See CHANGELOG.md for the new scenario, dependency migrations, setup
scripts, and known upgrade boundaries.

Start a scenario locally

Each scenario has its own aspire.config.json, so Aspire selects that scenario's AppHost
instead of inheriting the repository-root selection:```powershell
cd .\scenarios\18-BlazorAgenticUI
aspire start


Use `aspire run` for a foreground session, and `aspire stop` to stop the selected app.
Install the SDK requested by that scenario's nearest `global.json`: .NET 10.0.402 for
stable scenarios, or .NET 11 RC2 for Scenario 18. A .NET 11 installation does not satisfy
the stable .NET 10 pin. AppHost selection does not install SDKs or configure credentials.

To verify every scenario's local selection without starting services:```powershell
pwsh .\scripts\Tests\Test-ScenarioAppHosts.ps1

Installation

  1. Clone the repository:bash git clone https://github.com/Azure-Samples/eShopLite.git

  2. Navigate to the scenario directory of interest:bash cd eShopLite/scenarios/[scenario-folder]

  3. Login to Azure:shell azd auth login

  4. Provision and deploy all the resources:shell azd up

    It will prompt you to provide an azd environment name (like "eShopLite"), select a subscription from your Azure account, and select a location where the necessary models, like gpt-4.1-mini and ADA-002 are available, a sample region can be "eastus2".

Shared Microsoft Foundry models and local secrets

Use PowerShell 7 and sign in with az login. The new setup script creates or reuses an
AIServices account, deploys the common chat and embedding models, then configures local
AppHost user-secrets through the Aspire CLI. Supply your own subscription, resource group,
globally unique account name, and region:``powershell pwsh .\scripts\Initialize-FoundryModels.ps1
-SubscriptionId '<subscription-id>' -ResourceGroupName &#x27;rg-eshoplite&#x27;
-AccountName '<globally-unique-account-name>' -Location &#x27;eastus2&#x27;
-DryRun


Remove `-DryRun` to provision resources and write secrets. This can incur Azure charges.
`-DryRun` and `-WhatIf` make no Azure calls and do not establish model availability.

The default chat model and deployment name are **`gpt-6-luna`**; embeddings use
**`text-embedding-3-small`**. The script resolves model versions from the regional catalog
and checks SKU support and quota before provisioning. It stops if the requested model is
unavailable, with no automatic substitution. Override model/version, deployment name, SKU,
or capacity with the corresponding `-Chat*` and `-Embeddings*` parameters.
It reuses matching deployments and refuses to overwrite conflicting deployments or enable
key authentication on an account that disables it.

This provisions common model dependencies for local development, not every scenario&#x27;s
infrastructure. SQL/containers remain managed by each AppHost; Azure AI Search, realtime
audio, DeepSeek, GitHub Models, and other specialized dependencies still need their
scenario-specific setup. It does not change model declarations used by `azd up`.

### Configure secrets for existing deployments

Secret setup requires the SDK selected by each AppHost&#x27;s nearest `global.json`.
The script checks SDK availability before requesting a key. If using a nonstandard SDK
installation, pass `-DotNetRoot &quot;&quot;`; the override applies
only to child commands. An Aspire exit code 7 can indicate a missing SDK, not an Azure
authentication problem. Scenario 18 specifically requires .NET 11 RC2.

The existing `scripts\Set-AzureOpenAISecrets.ps1` configures secrets only, without creating
Azure resources. It discovers every `eShopAppHost.csproj`, including layouts without `src`,
and automatically includes future scenarios. Scenario 18 (`18-BlazorAgenticUI`) has its own
AppHost and independent user-secrets store, and is included automatically. Directories
without an AppHost are reported as skipped. Run from the **repo root**:```powershell
pwsh .\scripts\Set-AzureOpenAISecrets.ps1

The script interactively prompts for four values:

Prompt Parameter set
Azure OpenAI endpoint Parameters:AzureOpenAIEndpoint
Azure OpenAI API key (masked) Parameters:AzureOpenAIApiKey
Chat deployment name (default gpt-6-luna) Parameters:AzureOpenAIDeploymentName
Embeddings deployment name (default text-embedding-3-small) Parameters:AzureOpenAIEmbeddingsDeploymentName

Use -DryRun to preview the commands without executing them:```powershell
pwsh .\scripts\Set-AzureOpenAISecrets.ps1 -DryRun


For a preview without prompts or an API key:```powershell
pwsh .\scripts\Set-AzureOpenAISecrets.ps1 `
  -Endpoint &#x27;https://&lt;your-resource&gt;.openai.azure.com/&#x27; -NonInteractive -DryRun

Non-interactive writes additionally require -ApiKey as a SecureString, supplied from a
masked prompt or a secure credential source, not a plaintext key in command history.
Local .NET user-secrets are not an encrypted production secret store.

Internally, the script calls the Aspire CLI (aspire secret set) for each AppHost it discovers. To set a single value manually, use the same command directly:bash aspire secret set Parameters:AzureOpenAIEndpoint &quot;https://&lt;your-resource&gt;.openai.azure.com/&quot; \ --apphost scenarios/01-SemanticSearch/src/eShopAppHost/eShopAppHost.csproj

> Note: Scenario-specific extra parameters (e.g., Parameters:AzureOpenAIRealtimeDeploymentName in 03-RealtimeAudio, Parameters:DeepSeekEndpoint in 05-deepseek, Parameters:GitHubModelsToken in 11-GitHubModels) must still be set manually. See each scenario's README for details.

Quickstart

  1. Navigate to a specific scenario folder (e.g., scenarios/01-SemanticSearch/)
  2. Follow the README instructions in that scenario folder
  3. Run the solution using dotnet run in the appropriate host project folder

Demo

To run the demo, follow these steps:

  1. Navigate to the specific scenario folder
  2. Follow the "Run the solution" instructions in that scenario's README
  3. Access the application via the URLs provided in the console output

Sample Application

This is the eShopLite Aplication running, performing a Keyword Search:

This is the eShopLite Aplication running, performing a Semantic Search:

This is the eShopLite Application running the Realtime Audio feature:

This is the eShopLite Application using the DeepSeek-R1 Reasoning Model:

The Aspire Dashboard to check the running services:

The Azure Resource Group with all the deployed services:

Resources

  • Generative AI for Beginners .NET

  • Aspire Documentation

  • Azure OpenAI Service Documentation

Getting Help

If you get stuck or have questions about building AI apps, join:

If you have product feedback or errors while building, visit:

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
eShopLite 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

eShopLite 怎么在 Cursor、VS Code、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

eShopLite 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

eShopLite 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

eShopLite 支持哪些客户端?

资料标注支持 Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

eShopLite 能提供哪些能力?

资料显示能力标签包括 mcp、embeddings、semantic search、aspire、rag、azd。具体工具清单以官方文档为准。

eShopLite 需要什么运行环境?

运行时为 c#。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。