ecommerce-catalog-agent
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Ecommerce Catalog Agent
A conversational AI agent that answers product questions over an online store's catalog. It understands natural-language queries, finds matching products via hybrid search, and always reports live price and availability validated against the database.
Built as a tool-calling (ReAct) agent with a strict trust boundary: the model decides what to say and which products to show, but code owns the customer-facing numbers — so a hallucinated or injected price can never reach the user.
Features
Hybrid retrieval — BM25 (keyword) + vector embeddings (semantic) + Reciprocal Rank Fusion + cross-encoder reranking. Catches word forms and synonyms that exact matching misses (e.g. "взуття для бігу" → running shoes).
Filter-first — hard constraints (price, stock) are applied in SQL to build the candidate set before semantic ranking, avoiding the classic "top-k then filter → zero results" trap.
Two sources of truth — PostgreSQL is authoritative for volatile fields (price/stock); the vector index is a search cache only. Price and stock are re-fetched live before every answer.
Structured-output contract — the agent finishes by calling
present_resultswith product SKUs + prose; price/stock are filled by code from live SQL. The model has no field to write a number into → containment against hallucination and prompt injection ("attacker needs capability, not just instruction").Bounded agent loop — independent stoppers (max iterations, token budget, latency) plus deterministic, score-based escalation to a human operator (on the reranker confidence, never the model's self-report).
Conversation memory — per-session history for multi-turn context.
Custom MCP server — the catalog tools are exposed over the Model Context Protocol, so one contract serves the agent, an internal copilot, and Claude Desktop.
Multi-channel — a FastAPI
/chatservice, a Telegram bot via n8n (webhook), and a standalone aiogram bot (long-polling).Eval harness — a golden set scored with Recall@K / MRR to catch retrieval regressions with numbers, not vibes.
Related MCP server: Sneaker Catalog MCP Server
Architecture
Customer channels (Telegram / web / Claude Desktop)
│
[n8n] webhook intake + routing ── low confidence ──► human operator
│
[FastAPI /chat] models warmed at startup
│
[ReAct agent loop] bounded: max_iter / budget / latency
│ parse → retrieve → validate → respond
▼
[catalog tools] (also exposed as a custom MCP server)
search_products → hybrid BM25 + vector + rerank, filter-first
get_live_price / check_stock → live SQL
│
PostgreSQL (price/stock = truth) + Chroma (search cache)
▲
n8n schedule: XML feed → parse → upsert → re-embedTech stack
Python · FastAPI · OpenAI (LiteLLM-swappable) · PostgreSQL · Chroma · BM25 · sentence-transformers · cross-encoder reranker · custom MCP server · n8n · aiogram
Quick start
pip install -r requirements.txt
cp .env.example .env # fill OPENAI_API_KEY + PG_*
# create the schema, load the sample feed (builds the hybrid index)
psql -d catalog -f schema.sql
python ingest.py
# ask from the CLI
python agent.py "червоні кросівки до 2000 в наявності"
# or run the HTTP service
uvicorn api:app --port 8000 # → http://localhost:8000/docs
# or the Telegram bot (set TELEGRAM_BOT_TOKEN in .env)
python bot.pyProject layout
File | What |
| ReAct agent loop, bounded stoppers, structured-output contract |
| hybrid retrieval (BM25 + vector + RRF + cross-encoder) + confidence scores |
| read-only catalog tools + structured |
| the catalog tools exposed as a custom MCP server |
| FastAPI |
| standalone Telegram bot (aiogram, long-polling) |
| XML feed → PostgreSQL + rebuild the hybrid index |
| retrieval eval on a golden set (Recall@K / MRR) |
| Telegram → /chat → reply + escalation routing |
Design notes
Why hybrid, not pure vector — vector search alone can't honor exact filters (price/stock) or exact tokens (SKUs, model codes); BM25 + structured SQL cover what embeddings miss.
Why the vector index is never the source of price/stock — it's rebuilt on a schedule, so its copy of volatile fields is stale by design; the answer always re-validates against SQL.
Why MCP — the catalog tools are reused across consumers (the agent, an internal copilot, Claude Desktop): one contract, many clients.
The sample catalog and prompts are in Ukrainian; the agent replies in the customer's language.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Live product discovery for AI shopping agents, with shopper-approved retailer handoff.
Live product search for AI agents across Shopify merchants and major retailers.
AI-agent product catalog: search, lookup & purchase routing over verified merchant data.
The E-commerce Marketplace For Every AI Agent. A Governed Catalog Of 600M+ US Products, Plus Four Agent Ready Capabilities Search, Price Comparison, Product-Vs-Product, And Detailed Q&A.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables semantic search and natural language product recommendations using ChromaDB vector store and Azure OpenAI embeddings. Supports multi-filter search by category, brand, and price with 8 specialized MCP methods for intelligent product discovery.-
- FlicenseNot gradedqualityDmaintenanceProvides tools for searching a sneaker catalog (hybrid keyword and semantic search), retrieving product details, and checking inventory stock.-
- AlicenseNot gradedqualityBmaintenanceExposes product catalog and semantic search as tools for an LLM agent, enabling natural language product recommendations based on intent rather than keyword matching.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to provide e-commerce customer service with product search, RAG-based FAQ answers, human handoff, and automated security auditing with a review workflow.-