shoptet-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPTET_URL | Yes | The URL of the Shoptet e-shop admin to connect to. | |
| SHOPTET_EMAIL | Yes | The email address of the dedicated Shoptet admin user. | |
| SHOPTET_HEADED | No | Set to 1 to run the browser headed for development or live-admin testing. | 0 |
| SHOPTET_PASSWORD | Yes | The password of the dedicated Shoptet admin user. | |
| SHOPTET_ALLOW_WRITE | No | Set to 1 to enable write tools. Without it, write tools are not registered. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shoptet_shop_infoA | Log in and confirm which shop this server is connected to, and whether write tools are enabled. |
| shoptet_list_productsA | List products from the admin product list (id, name, price text). Optional case-insensitive name filter. |
| shoptet_get_productA | Name, visibility, short description and description of one product. Long texts are truncated to max_chars. |
| shoptet_get_price_listB | All variants of a product from its price list tab: variant id, name, code, price and stock. |
| shoptet_list_couponsC | Discount coupons (code, discount, template, validity, usage). Optionally filter by code. |
| shoptet_list_coupon_templatesA | Coupon templates you can pass as template_id when proposing a coupon. |
| shoptet_list_redirectsC | URL redirect rules (from, to). Optionally filter by source path. |
| shoptet_list_bannersC | Banners (id like "banner2", name, position). |
| shoptet_get_bannerB | HTML content and settings of one banner. |
| shoptet_get_html_codesA | Custom HTML code fields from Appearance → Editor → HTML code (header, footer, orderFinale, robotsFile, llmsFile). Omit field to get all. |
| shoptet_list_ordersA | Recent orders: id, code, date, status, total, shipping, payment, sales channel. Customer names, e-mails and addresses are never returned. |
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 11 tools
Most tools target clearly distinct resources or actions: product listing, product detail, price-list variants, coupons, coupon templates, redirects, banners, HTML codes, orders, and shop info. The only mild overlap is between product detail and price-list retrieval, but the descriptions make the distinction reasonably clear.
All tools use the same shoptet_ prefix and snake_case, and nearly all follow a predictable verb_noun pattern such as get_product, list_coupons, and get_banner. shoptet_shop_info is the main exception, but it is still readable and unambiguous.
Eleven tools is a well-scoped size for an admin inspection surface covering products, coupons, redirects, banners, HTML fields, orders, and shop identity. Each tool appears to earn its place without excessive fragmentation.
The surface is almost entirely read-only: it lists and gets products, coupons, redirects, banners, HTML codes, and orders, but there are no create, update, or delete operations for these resources. For an admin MCP, that is a significant lifecycle gap, especially since coupon templates are exposed but coupon creation is not.