MaxGaming MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_PROXY | No | Comma-separated list of hosts that should bypass the proxy (e.g., localhost,127.0.0.1). | |
| ALL_PROXY | No | Proxy URL used for all requests when no more specific proxy variable is set (e.g., http://proxy.example.com:8080). Special characters in proxy credentials must be URL-encoded. | |
| HTTPS_PROXY | No | Proxy URL for HTTPS requests (e.g., http://user:pass@proxy.example.com:8080). Special characters in proxy credentials must be URL-encoded (e.g., @ → %40). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Search MaxGaming storefronts. Use list_storefronts to discover supported countries and shop languages. Use search_products to find products by name, model or keyword and get_product to resolve exact product URLs or article numbers. MaxGaming is an online-only retailer; no physical stores or pickup. Prices and availability can change.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storefrontsA | List supported countries, languages, currencies and regions for MaxGaming. |
| search_productsA | Search the selected MaxGaming storefront. Results and total_products may include products unrelated to the query. Brand, price and availability filters are applied locally per page. Sort order and include_details are optional. Use get_product for exact URLs or article numbers. |
| browse_pageB | Browse a MaxGaming category, brand or campaign page. Returns visible products with embedded data. |
| get_productA | Read product details from a MaxGaming product page by URL or article number, including description, images, specifications, variants and availability. Returns found=false for a 404 or missing product. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct action: configure storefront, keyword search, browse a known category/brand page, and fetch a single product by URL/article number. The only mild overlap is search_products vs. browse_page, but the descriptions clarify that browsing requires a known category/brand path while search takes a query, so an agent can pick correctly.
All four tools follow a clean snake_case verb_noun pattern (list_storefronts, search_products, browse_page, get_product). The verbs are precise and non-redundant, making the naming predictable.
Four tools is on the lean side but each covers a genuinely different step of the discovery flow (configure, search, browse, inspect). Nothing is redundant, though the surface is small enough that users may want a few more capabilities.
The read-only browsing lifecycle (storefront selection, search, category browse, product detail) is covered, but there is no way to enumerate categories/brands/campaigns without already having a path, no cross-storefront price or availability comparison, and no cart/order operations. These are workable gaps for a research-only tool but notable ones.