sellabot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READ_ONLY | No | Set to 'true' to expose only read-only tools. Default is false. | false |
| SHOPEE_ENV | No | Environment: production or sandbox. Default is production. | production |
| SHOPEE_REGION | No | Shopee region code (e.g., MY, SG, TH). Default is MY. | MY |
| SHOPEE_SHOP_ID | Yes | Your Shopee shop ID (obtained after authorization). | |
| SHOPEE_PARTNER_ID | Yes | Your Shopee partner ID. | |
| SHOPEE_PARTNER_KEY | Yes | Your Shopee partner key. | |
| TOKEN_ENCRYPTION_KEY | Yes | Key used to encrypt stored tokens. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsB | List or search products in the shop, optionally filtered by status. |
| create_listingA | Create a new product listing in the shop. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| update_listingA | Edit an existing listing's content (name, description, images, etc.). [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| delete_listingA | Remove a product. Defaults to unlisting (reversible) rather than permanent deletion. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_priceC | Get the current price of a product and each of its variants. |
| update_priceA | Set the price for one product or a specific variant. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| bulk_update_priceA | Set prices for many products/variants in one call. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_stockB | Get current stock for a product and each of its variants. |
| get_low_stock_itemsA | List items at or below a stock threshold (default 5). |
| update_stockA | Set the stock quantity for one product or a specific variant. [ROUTINE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_messagesA | List buyer conversations, optionally only unread ones. |
| reply_to_messageA | Send a reply in a buyer conversation. [ROUTINE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_reviewsB | List product reviews/ratings, optionally filtered by product, rating, or reply state. |
| reply_to_reviewB | Post a public seller reply to a product review. [ROUTINE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_ordersB | List orders, optionally filtered by fulfillment status. |
| get_orderA | Full detail for one order: line items, buyer, ship-to address, totals, and status. |
| get_shipping_infoB | Shipping requirements for an order: carrier, pickup/drop-off, ship-by deadline, parcel specs, pickup address. |
| track_shipmentC | Current tracking status and checkpoints for a shipped order. |
| arrange_shipmentA | Book courier pickup or drop-off for an order. This is the digital step — the seller still physically hands over the parcel. [CRITICAL] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_shipping_documentA | Generate/fetch the shipping label (airway bill) for a confirmed shipment. [ROUTINE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_returnsB | List buyer return/refund requests. |
| get_returnA | Full detail of one return/refund request: reason, evidence, amount, buyer. |
| respond_to_returnA | Accept or reject a return/refund request (optionally a partial amount). Always requires the seller's explicit approval. [CRITICAL] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_cancellationsB | List buyer-initiated cancellation requests. |
| respond_to_cancellationA | Accept or reject a buyer's cancellation request. Always requires the seller's explicit approval. [CRITICAL] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_disputesA | List disputes/complaints/escalations needing seller input. |
| respond_to_disputeB | Submit the seller's response/evidence to a dispute or complaint. Always requires the seller's explicit approval. [CRITICAL] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_vouchersA | List shop vouchers/discounts, optionally filtered by status. |
| create_voucherA | Create a shop or product voucher. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| boost_listingA | Boost/feature a listing where the platform supports it. [SENSITIVE] This action changes live shop data and requires the seller's explicit confirmation before it executes. |
| get_shop_infoB | Shop profile, region, status, and auth health. |
| get_shop_performanceC | Shop KPIs: sales, orders, rating, response rate, penalties. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RextonWong/sellabot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server