Mcp Shopee

io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Nov 10, 2026

MCP server for Shopee — LatAm marketplace Partner API v2 (orders, products, shipping, returns)

Overview

AI-generated overview

MCP server for the Shopee marketplace Partner API v2, letting an assistant read and manage a seller's orders, products, shipping, returns and promotions.

What you can do
  • Read shop info and list or inspect orders, including full detail for up to 50 order numbers
  • Manage fulfillment: arrange shipments, fetch shipping parameters, tracking numbers and label PDFs, cancel unshipped orders
  • List, create, update and delete products, and change stock levels and prices for items or variants
  • List and act on return/refund requests, including confirming returns and accepting buyer offers
  • Create shop-level discounts and bundle-deal promotions
  • Send text or sticker messages to buyers in Shopee seller chat
When to use it
Useful for LatAm sellers who run a Shopee shop and want an assistant to triage orders, keep stock and prices current, handle shipping and returns, or set up promotions without switching between dashboards.
Requirements
Runs locally over stdio via the npm package (Node.js), or over HTTP with MCP_HTTP and MCP_PORT for server-to-server testing. Needs a registered Shopee Open Platform app: SHOPEE_PARTNER_ID, SHOPEE_PARTNER_KEY, SHOPEE_SHOP_ID and SHOPEE_ACCESS_TOKEN, plus optional SHOPEE_ENV for sandbox or production. The access token must be obtained and refreshed outside this server.
Before you install
Requires the secret partner key and a merchant access token, which grants write access to the shop. Many tools change live data: creating, updating and deleting products, changing prices and stock, shipping and cancelling orders, confirming returns, creating promotions and messaging buyers. The access token expires every four hours and refreshing it is out of scope. The README notes some endpoint payloads are unvalidated against Shopee's docs, so verify before production use.

Installation

In SourceWeft

  1. Open Mcp Shopee in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-shopee

MCP server for Shopee — the Shopee Open Platform Partner API v2.

Shopee is one of the two marketplaces where LatAm merchants concentrate the bulk of their online GMV (dominant in Brazil, rapidly expanding across the region). Paired with @codespar/mcp-mercadolibre, this package gives agents full reach across LatAm's major ecommerce marketplaces — each has its own seller ecosystem, so merchants typically operate on both.

Tools (22)

ToolPurpose
get_shop_infoGet basic information about the authorized Shopee shop (shop_name, region, status, auth expiry).
list_ordersList orders within a time window, optionally filtered by order_status.
get_order_detailGet full detail for one or more orders by order_sn (comma-separated, up to 50).
ship_orderArrange shipment for an order — either request pickup, drop off, or pass a tracking number depending on the...
cancel_orderCancel an order that has not yet shipped.
list_productsList items (products) in the shop with optional status filter.
get_product_detailGet detailed base info for up to 50 items by item_id.
update_product_stockUpdate stock levels for an item (or its models/variants).
update_product_priceUpdate prices for an item (or its models/variants).
get_shipment_listList orders currently in shipment (status SHIPPED or in-transit).
get_return_listList return/refund requests on the shop, optionally filtered by status and time window.
confirm_returnConfirm (accept) a buyer-initiated return request by return_sn.
add_itemCreate a new product (item) in the shop.
update_itemUpdate an existing product.
delete_itemDelete an item (product) from the shop by item_id.
get_shipping_parameterFetch the required shipping parameters for an order before calling ship_order.
get_tracking_numberGet the tracking number (and courier info when available) for a shipped order.
download_shipping_documentRequest the shipping label / air waybill PDF for one or more orders.
accept_return_offerAccept the buyer's return offer (proposed solution) for a return_sn, ending negotiation in the buyer's favor.
add_discountCreate a new shop-level discount (promotion) with a time window.
add_bundle_dealCreate a bundle-deal promotion (e.g.
send_chat_messageSend a text or sticker message to a buyer in Shopee's seller chat.

Install

bash
npm install @codespar/mcp-shopee@alpha

Environment

bash
SHOPEE_PARTNER_ID="2001234"        # partner_id (integer) from Shopee Open PlatformSHOPEE_PARTNER_KEY="..."           # partner_key (secret) for HMAC signingSHOPEE_ACCESS_TOKEN="..."          # merchant access_token (4h lifetime; refresh via refresh_token)SHOPEE_SHOP_ID="123456789"         # shop_id (integer) from authorization flowSHOPEE_ENV="production"            # or "sandbox"

Authentication

Shopee uses partner-signed requests. For shop-level endpoints the signature is:

base_string = partner_id + api_path + timestamp + access_token + shop_idsign        = hex(HMAC_SHA256(partner_key, base_string))

partner_id, timestamp, access_token, shop_id, and sign are attached as URL query parameters on every request. The signing helper (src/index.ts) handles this on each call.

The access_token is obtained via the merchant authorization OAuth flow on Shopee Open Platform; it expires every 4 hours. Refresh it using the refresh_token (30-day lifetime) — that exchange lives outside this MCP's scope, typically in a separate token-management service.

Run

bash
# stdio (default — for Claude Desktop, Cursor, etc)npx @codespar/mcp-shopee
# HTTP (server-to-server testing)MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-shopee

Base URLs

  • Production: https://partner.shopeemobile.com/api/v2
  • Sandbox: https://partner.test-stable.shopeemobile.com/api/v2

Select with SHOPEE_ENV.

Status

0.1.0-alpha.1 — Shopee's Partner API documentation portal requires developer registration, so some endpoint payloads and field-level contracts (especially around ship_order pickup/dropoff objects and logistics channel specifics) should be validated against the live docs before production use. The signing recipe and base-URL selection are implemented to spec.

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/ecommerce/shopee/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0-alpha.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts