galaxus-mcp
Allows AI assistants to search products, get full product details, check price availability, compare products, and browse categories on Galaxus (and Digitec) using internal GraphQL endpoints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@galaxus-mcp search for Sony WH-1000XM5 headphones"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
galaxus-mcp
An unofficial Model Context Protocol server that lets AI assistants (Claude, ChatGPT, and any other MCP client) search products and read product details from Galaxus / Digitec.
⚠️ Unofficial / use at your own risk. Galaxus does not offer a public API. This server talks to the same internal GraphQL endpoints their website uses, so there's no stability guarantee: Galaxus can change the schema, rotate the persisted-query ids, or block traffic at any time. Respect their Terms of Service and
robots.txt, keep request volume low, and don't use this to resell their data. Provided as-is under the MIT license with no affiliation to Digitec Galaxus AG.
Tools
Tool | Description |
| Search the catalog by keyword. Returns name, brand, price (CHF), rating, availability, image, and URL, plus category facets and a |
| Full details for a single product by numeric id, slug, or full URL: description, GTIN, specifications, images, and price history (current position vs recent low/high). |
| Lightweight price + stock snapshot (incl. price-history position) for one product. Handy for price tracking. |
| Fetch full details for 2–8 products at once for side-by-side comparison. |
| Browse a category by name, sorted/filterable, with available-brand and product-type facets to help refine. |
Related MCP server: galaxus-mcp
How it works
Galaxus's storefront is a Next.js + Relay app backed by a HotChocolate (.NET) GraphQL server. Queries are persisted: the client sends a hash + variables, not the query text.
Search / category →
POST /graphql/o/<searchQueryHash>/useSearchDataQueryProduct / price →
POST /graphql/o/<productQueryHash>/productDetailPageQuery
Both require the headers X-Dg-Portal and X-Dg-Language. The product HTML pages are gated
behind a CAPTCHA for non-browser clients, but the GraphQL endpoint is not, so this server uses
GraphQL for every operation. Search uses skipRedirect so category-like terms still return a
product list, supports cursor pagination, and exposes the brand / product-type facets. Every
request goes through a small rate limiter, a short-lived response cache, and a timeout.
Install
npm install
npm run buildUse with Claude Code
claude mcp add galaxus -- node /absolute/path/to/galaxus_mcp/dist/index.jsUse with Claude Desktop / other MCP clients
Add to your client's MCP config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"galaxus": {
"command": "node",
"args": ["/absolute/path/to/galaxus_mcp/dist/index.js"]
}
}
}Configuration (env vars)
Variable | Default | Notes |
|
|
|
| per-site |
|
| per-site |
|
| captured | persisted id for |
| captured | persisted id for |
|
| min delay between requests |
|
| response cache TTL |
|
| per-request timeout |
| Chrome UA | sent with every request |
Refreshing the persisted-query ids
If search or product calls start failing (e.g. after a Galaxus deploy), the persisted-query hashes have likely rotated. To recapture them:
Open https://www.galaxus.ch in Chrome with DevTools → Network.
Search for something, then open a product page.
Find the requests to
/graphql/o/<hash>/useSearchDataQueryand/graphql/o/<hash>/productDetailPageQuery.Set
GALAXUS_SEARCH_HASH/GALAXUS_PRODUCT_HASHto the new<hash>values.
Project layout
src/
index.ts MCP server + tool registration
config.ts env-driven config (site, portal, hashes, rate limits)
types.ts normalized models + DataProvider interface
http.ts HTTP client (throttle + cache + timeout)
providers/
graphql.ts internal-GraphQL providerThe tools talk to a DataProvider interface rather than the GraphQL client directly, so the
data source can be swapped out later if the internal API stops working.
License
MIT
Available Tools
5 toolscheck_price_availabilityCheck price & availabilityA
Lightweight price + stock snapshot for one product (id, slug, or URL), including price-history position (whether the current price is low/high vs the recent range). Ideal for price tracking.
Inputs: idOrUrl (required).
compare_productsCompare Galaxus productsA
Fetch full details for several products at once (by id, slug, or URL) for side-by-side comparison. Returns one detail object per input.
Inputs: idsOrUrls (required).
get_productGet Galaxus product detailsA
Fetch full details for a single product by its numeric id, slug, or full product URL: description, GTIN, specifications, images, rating, availability, and price history.
Inputs: idOrUrl (required).
list_categoryBrowse a Galaxus categoryA
Browse products in a category by name (e.g. 'ssd', 'office chair'), sorted and filterable. Returns products plus facets (available brands and product types) to help refine, and a nextCursor for paging.
Inputs: category (required), sort, brand, limit, +3 more.
search_productsSearch Galaxus productsA
Search the Galaxus / Digitec catalog by keyword. Returns matching products with price (CHF), rating, availability, and URL, plus a nextCursor for pagination.
Inputs: query (required), sort, brand, limit, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: search, browse by category, single product details, lightweight price check, and multi-product comparison. Some overlap exists between get_product, compare_products, and check_price_availability, but descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case: search_products, get_product, check_price_availability, compare_products, list_category. The naming is predictable and clear.
With 5 tools, the server is well-scoped for product discovery, detail retrieval, price tracking, and comparison. The count is within the ideal range and each tool earns its place.
The tool surface covers the core catalog lifecycle: search, category browsing, single product details, price/availability checks, and product comparison. Minor gaps like an explicit category listing or bulk search are missing, but agents can work around these.
Maintenance
Related MCP Connectors
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
Compare prices across Swiss and European shops — barcode (GTIN) lookup and daily price history.
Product search for AI shopping agents: prices and buy links from big retailers. No key needed.
Search and look up products across thousands of online stores, normalized into one schema.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.2MIT
- AlicenseAqualityDmaintenanceEnables product search and discovery on Galaxus and Digitec, with tools for searching, browsing, comparing, and looking up prices and specifications.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.8MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search Digikala's catalogue, compare every seller's offers and prices, review ~30 days of price history, read customer reviews and Q&A, and surface current deals, all through read-only tools.23670 PyPI43PolyForm Noncommercial 1.0.0