Omisell MCP Server

Read your Omisell seller data — orders, shipments, products and stock, returns, payments, warehouses and sales channels — from Claude, and propose product changes that you approve inside Omisell. Every tool is scoped to the business the token was issued for.

Server URL: https://mcp.omisell.com/mcp

Tools: 65 total — 45 read-only, 18 write previews (dry_run_*, read-only), 2 write proposals (propose_*, create an approval-pending request; nothing changes until you approve it in Omisell).

Why use it

Ask Claude about your store in plain language instead of clicking through the portal: how many orders are stuck, which SKUs are out of stock, why a shipment is delayed, this week's sales by channel — and, with your approval, activate products or update prices.

What you can ask

"How many orders are stuck in packing right now?"

"Which products are out of stock in the Hanoi warehouse?"

"Why is shipment SPXVN0123 delayed?"

"Show this month's sales by sales channel."

"Propose deactivating these 5 SKUs" (you approve it in Omisell).

Setup

claude.ai and Claude Desktop

Settings → Connectors → Add custom connector.

Name it Omisell and paste the server URL https://mcp.omisell.com/mcp.

Click Connect — a browser tab opens for Omisell sign-in.

Verify with: "What Omisell tools are available?"

Claude Code

Connecting more than one Omisell account at once

claude.ai identifies a connector by its URL, so to keep several accounts connected at the same time, give each its own URL by adding any label after /mcp/:

Account 1:  https://mcp.omisell.com/mcp/shop-a
Account 2:  https://mcp.omisell.com/mcp/shop-b

The label is just a name so the clients stay separate — it does not pick the account. You choose which account during the sign-in step, so add /mcp/shop-a and sign in with account A, then add /mcp/shop-b and sign in with account B. The label may be any of A–Z a–z 0–9 _ - (max 64 chars). The plain https://mcp.omisell.com/mcp keeps working for a single account.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth will work — point it at the server URL above.

Available tools

All read tools query your own business's data only. The dry_run_* tools are read-only previews of a write; the propose_* tools create a request you approve inside Omisell.

Orders

Tool	Scope	What it does
`order_fee_breakdown`	`read_order`	Every fee line on specific orders — commission, shipping, vouchers, adjustments. Pass one or more order tracking codes.
`find_problem_orders`	`read_order`	Orders matching known problem patterns in the last N days: no shipment, stuck status, fee mismatch, missing payment.
`return_pipeline_state`	`read_order`	Where returns sit in the pipeline over a window — requested, in transit, received, refunded.
`fee_aggregate_by_channel`	`read_order`	Total fees per sales channel over a period, optionally filtered to specific fee codes.
`inbound_receiving_status`	`read_order`	Inbound shipments to the seller's warehouses over a window and how much of each has been received.
`get_order_timeline`	`read_order`	Every status change on one order, in order, with timestamps. Pass `tracking_code` — the order code, e.g. ODVN…

Payments

Tool	Scope	What it does
`find_overdue_payment_orders`	`read_order`	Orders with a payment overdue, in debt or only partly paid, older than N days.
`payment_status_breakdown`	`read_order`	Orders per payment status over a period, grouped by channel or payment type.

Returns

Tool	Scope	What it does
`list_order_returns`	`read_order`	This seller's return slips over a window, newest first, optionally filtered by status.
`order_return_detail`	`read_order`	Everything on one return slip: status, refund amount, reason, dispute notes and the order it belongs to. Pass `return_code` — the return tracking code, e.g. RTNVN…
`return_aging_summary`	`read_order`	Open returns bucketed by how long they have been open.

Shipments

Tool	Scope	What it does
`diagnose_shipment_issue`	`read_shipment`	Explain why one shipment is stuck or failed, with the evidence: status history, courier responses, fulfilment pushes. Pass `tracking_code` — the shipment code, e.g. SPVN…
`get_shipment_journey_timeline`	`read_shipment`	Every status change on one shipment, in order, with timestamps. Pass `tracking_code`. Expensive — call it for a specific shipment, not in a loop.

Dropship

Tool	Scope	What it does
`aggregate_dropships`	`read_order`	Count and total dropship orders over a window, grouped by vendor or status. Dropship is a Philippines-only product today.
`dropship_sla_breach`	`read_order`	Dropship orders past their fulfilment or shipping SLA and not yet finished, soonest-breached first.
`dropship_settlement_aging`	`read_order`	Dropship orders shipped but not yet settled, bucketed by age. Requires the business owner's own token.
`vendor_dropship_volume`	`read_order`	Dropship order count and value per vendor over a window.
`dropship_3pf_push_failures`	`read_order`	Dropship orders that failed to reach the fulfilment provider and have been retried at least N times.

Inventory

Tool	Scope	What it does
`stock_on_hand`	`read_product`	Available, reserved and incoming stock for one SKU across the seller's warehouses. Pass `sku`.
`list_out_of_stock_products`	`read_product`	Products at or below a stock threshold in specific warehouses. Pass `pickup_address_ids` — get them from `list_pickup_addresses`.

Products

Tool	Scope	What it does
`search_products`	`read_product`	Find this seller's products by name, SKU or barcode, with price and stock.
`product_detail`	`read_product`	Full detail of one product: variants, prices, stock per warehouse, channel listings. Pass `sku`.
`find_flashsale_price_warnings`	`read_product`	Flash-sale items priced suspiciously far below their normal price — the check the seller portal shows as a warning.

Channel listings

Tool	Scope	What it does
`list_product_stores`	`read_product_store`	This seller's channel listings, one per SKU per sales channel: store, sku, external id, status, price and channel stock. Only listings on an active sales channel are returned. Optional filters: store_ids, platforms, keyword, status.

Sales channels

Tool	Scope	What it does
`list_stores`	`read_store`	The seller's connected sales channels (Shopee, Lazada, TikTok, web, …), whether each is active and what it syncs. Start here when another tool needs a store id.
`store_detail`	`read_store`	Full detail of one connected sales channel: platform, sync flags, warehouse mapping. Pass `store_id` (from `list_stores`) or `external_channel_code`.

Warehouses

Tool	Scope	What it does
`list_pickup_addresses`	`read_pickup`	The seller's warehouses (pickup addresses), with their fulfilment provider and whether each is active. Start here when another tool needs a warehouse id.
`pickup_address_detail`	`read_pickup`	Full detail of one warehouse: address, contact, fulfilment provider, flags. Pass `pickup_address_id` — get it from `list_pickup_addresses`.

Aggregation & reports

Tool	Scope	What it does
`aggregate_orders`	`read_order`	Count and total this seller's orders over a date window, optionally grouped by status, sales channel or warehouse. Use for 'how many orders', revenue roll-ups and channel comparisons.
`aggregate_shipments`	`read_shipment`	Count shipments over a date window, grouped by status, courier or warehouse. Use for delivery-progress and courier-mix questions.
`sales_summary`	`read_order`	Gross and net sales for a period, grouped by channel, day or warehouse. The headline numbers a seller asks for first.
`top_skus`	`read_order`	Best-selling SKUs over a window, by quantity or by revenue.
`cancel_analysis`	`read_order`	Cancelled orders over a window, broken down by reason and channel.
`return_analysis`	`read_order`	Returns over a window, broken down by reason code and channel.
`oos_summary`	`read_product`	How often and for how long products were out of stock over a window.
`courier_performance`	`read_shipment`	Delivery success rate, lead time and return rate per courier over a window.
`find_pending_shipment_orders`	`read_order`	Orders that are confirmed but have no shipment yet, oldest first. Use to find what is stuck before dispatch.
`find_stuck_shipments_summary`	`read_shipment`	Shipments that have not changed status for longer than expected, grouped by where they stalled.
`sales_by_channel`	`read_order`	Revenue and order count per sales channel for a period. Requires the business owner's own token — staff cannot read it.
`sell_through_rate`	`read_order`	Units sold against units received per product over a period.
`dead_stock_summary`	`read_order`	Products holding stock with no sale for N days, and the value tied up in them.
`discontinue_candidates`	`read_order`	Products that are OUT OF STOCK and had no order in N days — candidates for discontinuing. Returns the product, how many channel listings link to it, and the last order time.
`inventory_abc_analysis`	`read_order`	Classify products into A/B/C bands by revenue or quantity contribution over a period.
`fulfillment_lead_time`	`read_order`	Time from order confirmation to hand-over and to delivery, over a period.
`dispatch_volume_by_warehouse`	`read_shipment`	Packages dispatched per warehouse over a period.

Write previews (read-only)

Each previews which items are eligible for a write and changes nothing.

Tool	Scope	What it does
`dry_run_update_product_active`	`read_product`	Preview which of the given SKUs are eligible to be activated or deactivated, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_update_product_price`	`read_product`	Preview which of the given SKUs are eligible for a sale-price update, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_set_product_tag`	`read_product`	Preview which of the given SKUs are eligible to have tags added or removed, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_mark_oos_products`	`read_product`	Preview which of the given SKUs are currently active and eligible to be marked out of stock, and which are already inactive, out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_push_product_store_to_channel`	`read_product_store`	Preview which of the given channel listings are eligible to be pushed to their sales channel, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_update_channel_price`	`read_product_store`	Preview which of the given channel listings are eligible for a price update on their sales channel, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_update_channel_stock`	`read_product_store`	Preview which of the given channel listings are eligible for a stock update on their sales channel, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_mark_oos_on_channel`	`read_product_store`	Preview which of the given channel listings are eligible to be marked out of stock on their sales channel, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_sync_product_store_status`	`read_product_store`	Preview which of the given channel listings are eligible for a status sync with their sales channel, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_cancel_shipments`	`read_shipment`	Preview which of the given shipments would be cancelled and the effect. Preview only; execution is not available on this connector.
`dry_run_get_labels`	`read_shipment`	Preview which of the given shipments are in scope for retrieving a shipping label, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_push_shipments_to_3pl`	`read_shipment`	Preview which of the given shipments are eligible to be pushed to the fulfilment provider, and which are not. Preview only; execution is not available on this connector.
`dry_run_sync_shipments_tracking`	`read_shipment`	Preview which of the given shipments are in scope for a tracking sync with the courier, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_retry_ship_pickup`	`read_shipment`	Preview which of the given shipments are eligible for a pickup retry, and which are out of scope or not found. Preview only; execution is not available on this connector.
`dry_run_update_shipment_status`	`read_shipment`	Preview which of the given shipments may transition to the target status and which are blocked, with the current status and the reason for each block. Preview only; execution is not available on this connector.
`dry_run_update_gifts_for_orders`	`read_order`	Preview which of the given orders can still have their gift items changed, because no shipment has been created for them yet. Preview only; execution is not available on this connector.
`dry_run_update_shipping_rule_orders`	`read_order`	Preview which of the given orders can still have their courier reselected via a shipping rule. Preview only; execution is not available on this connector.
`dry_run_update_pickup_by_priority`	`read_order`	Preview which of the given orders can still have their warehouse reassigned by priority, because no shipment has been created for them yet. Preview only; execution is not available on this connector.

Write proposals (you approve in Omisell)

These create an approval-pending request; the change happens only after you approve it on an Omisell surface. They require the write_product scope, which you grant on the consent screen.

Tool	Scope	What it does
`propose_update_product_active`	`write_product`	Propose activating or deactivating products by SKU. Creates a request the shop owner must approve in Omisell before it takes effect — nothing changes until then. Preview with dry_run_update_product_active first.
`propose_update_product_price`	`write_product`	Propose a new sale price for products by SKU. Creates a request the shop owner must approve in Omisell before it takes effect — nothing changes until then. Preview with dry_run_update_product_price first.

Security

OAuth 2.1 with PKCE; sign-in is your real Omisell portal login.

Every token is bound (RFC 8707) to the exact connector URL it was issued for, so a token for one connector cannot be used at another.

Read tools are read-only; writes are never automatic — a propose_* tool only creates a request that a human approves in Omisell.

Per-token rate limiting; buyer PII is not exposed.

Troubleshooting

"unknown client" / cannot connect: re-add the connector; the server supports dynamic client registration, so no client id is needed.

A labelled URL returns 404: the label must match [A-Za-z0-9_-]{1,64} (no dots or slashes).

401 after a while: access tokens are short-lived; the client refreshes automatically if you granted offline access.

FAQ

Does it change my data? Only through a propose_* tool, and only after you approve the request in Omisell. Everything else is read-only.

Can I connect two shops? Yes — see Connecting more than one Omisell account at once.

Why use it#

What you can ask#

Setup#

claude.ai and Claude Desktop#

Claude Code#

Connecting more than one Omisell account at once#

Other MCP clients#

Available tools#

Orders#

Payments#

Returns#

Shipments#

Dropship#

Inventory#

Products#

Channel listings#

Sales channels#

Warehouses#

Aggregation & reports#

Write previews (read-only)#

Write proposals (you approve in Omisell)#

Security#

Troubleshooting#

FAQ#