Unofficial Model Context Protocol server for Tebex stores — read catalog & store ops, run AI store audits. Not affiliated with Tebex Ltd.
Solid foundation with 25 well-named tools covering catalog, operations, and audit workflows. All tools have descriptions (avg 156 chars) and input schemas with types. However, parameter descriptions are inconsistent, many lack detail on constraints, formats, or dependencies. Output schemas are undocumented. Error handling is basic (TebexError exists but recovery guidance is minimal). Tool composition is good (single responsibility, chainable IDs), but some tools like tebex_store_snapshot aggregate multiple concerns. Security is well-handled (credentials via env/headers, no secrets in params). Naming follows verb_noun convention consistently.
Ban a user from the store. Plugin API POST /bans.
Create a coupon code. Plugin API POST /coupons.
Create a gift card with a starting balance. Plugin API POST /gift-cards.
Create a manual payment (delivers package commands as a normal purchase would). Plugin API POST /payments. `packages` is an array like [{ id, options? }]. Use tebex_list_packages and the payment fields endpoint to learn required options first.
List a customer's active (non-expired) purchased packages. Plugin API GET /player/{id}/packages. Useful for support lookups.
Delete a coupon by ID. Plugin API DELETE /coupons/{id}.
Output schemas undocumented. No tool describes what fields are returned or their types. LLMs cannot plan downstream calls or extract required IDs without trial-and-error.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Get a single category by ID, optionally including its packages. Headless API.
Get a single coupon by ID. Plugin API GET /coupons/{id}.
Get a gift card by ID, or by code via the codeLookup flag. Plugin API GET /gift-cards/{id} or /gift-cards/lookup/{code}.
Get a single package (product) by its identifier — price, description, type, sale info. Headless API.
Retrieve a single payment by its transaction ID. Plugin API GET /payments/{transaction}.
List all bans on the account. Plugin API GET /bans.
List all categories in the webstore. Set includePackages to also return every package (product) within each category — the fastest way to pull the whole catalog for analysis. Uses the Headless API (needs TEBEX_PUBLIC_TOKEN).
List community goals and their progress. Plugin API GET /community_goals.
List all coupons (auto-paginated). Plugin API GET /coupons.
List all gift cards with balances. Plugin API GET /gift-cards.
List all packages (products) in the webstore with prices and descriptions. Headless API.
List recent payments/orders (most recent first, up to limit). Plugin API GET /payments.
List all active sales/discounts on the store. Plugin API GET /sales. (Sales can be read but not created via API.)
Look up a player/customer and their purchase summary. Plugin API GET /user/{id}.
Get account/store information: store name, domain, currency, server, owner. Plugin API GET /information. Good first call to confirm credentials and currency.
Get the live store listing (categories + packages currently for sale) as the Plugin API sees it. Plugin API GET /listing.
Aggregate the whole store in ONE call for analysis: store info, full catalog (categories + packages), active sales, recent payments, and coupons. Use this to audit a store (pricing gaps, empty categories, stale/expired coupons, discount coverage, revenue mix) and hand the user concrete recommendations. Partial results are returned if some credentials or endpoints are unavailable.
Add balance to an existing gift card. Plugin API PUT /gift-cards/{id}.
Void (disable) a gift card. Plugin API DELETE /gift-cards/{id}.
Parameter descriptions lack constraint details. E.g., 'limit' in tebex_list_payments says '1-100, default 100' in description but no min/max schema constraints. 'discount_percentage' in tebex_create_coupon has no range guidance (0-100? 0-1?). Format strings (dates as yyyy-mm-dd) are mentioned but not formalized.
tebex_store_snapshot aggregates 5+ concerns (store info, catalog, sales, payments, coupons). While useful for audits, it violates single-responsibility principle and makes error handling ambiguous (which component failed?). Consider splitting or documenting partial-failure behavior.
Error handling is minimal. TebexError exists but tool descriptions do not explain recovery paths. E.g., 'TEBEX_SECRET is not set' error is clear, but what if a payment lookup fails? Should the agent retry, search by date, or ask the user? No guidance.
Destructive tools (tebex_delete_coupon, tebex_void_giftcard) lack confirmation or dry-run support. Agents can irreversibly delete coupons or void gift cards without a safety gate. Consider adding a 'confirm' parameter or separate 'preview' tools.