shipsaving-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIPSAVING_APP_KEY | Yes | ShipSaving App Key (sk_ prefix) | |
| SHIPSAVING_LOG_FILE | No | Path to log file (logs go to stderr by default) | |
| SHIPSAVING_TIMEOUT_MS | No | Request timeout in milliseconds | 60000 |
| SHIPSAVING_API_BASE_URL | No | API base URL | https://app-gateway.shipsaving.com |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_shipping_ratesA | 获取多承运商运费报价比价。需提供寄件地址、收件地址、包裹信息和 ship_date。返回所有可用运费方案，标记最便宜和最快选项。 |
| search_shipmentsB | 搜索运单列表，支持多种条件筛选 |
| get_shipment_detailC | 查看运单详细信息 |
| track_shipmentC | 通过追踪号查询物流状态 |
| get_insurance_ratesA | 查询保险价格。根据保额和服务等级返回保险费率信息。 |
| create_draft_shipmentA | 标准下单流程第二步：创建运单草稿（不立即付款）。在 get_shipping_rates 之后、pay_shipment 之前调用。保存地址和包裹信息，等用户确认后再付款。 |
| pay_shipmentB | 对已选报价的运单进行支付，生成面单。可选附带保险信息。 |
| void_labelB | 退款/作废未使用的面单 |
| search_ordersA | 搜索订单列表，支持按状态、店铺、日期、关键词等筛选。当用户提供了类似 ID 的内容（如订单号、追踪号、订单ID等），必须通过 hybrid 参数传入进行搜索。 |
| get_order_detailD | 查看订单详细信息 |
| create_orderA | 手动创建订单。【重要】调用此接口前必须先准备好所有信息：1) 如果用户指定了地址簿ID，先调用 list_addresses 获取该地址的完整信息；2) 确认订单号、商品信息（名称、数量、单价）齐全；3) 缺少任何必填信息时必须先向用户询问，不得传空值调用接口。 |
| buy_label_from_orderA | 通过已有订单打单（购买面单）。当用户要对订单打单时，必须使用此工具，不得使用 create_draft_shipment + pay_shipment 流程。需要先通过 get_shipping_rates 获取 rate_id。 |
| mark_order_shippedB | 标记订单为已发货状态 |
| cancel_orderC | 取消订单 |
| sync_store_ordersA | 手动触发店铺订单同步。同步成功后，必须立即调用 search_orders（传入相同的 store_id，status 为 AWAITING）查询刚同步过来的订单并展示给用户。 |
| get_order_tagsB | 查询所有订单标签 |
| list_addressesC | 查询地址簿中的地址列表 |
| create_addressB | 在地址簿中新建地址 |
| update_addressB | 编辑/更新地址簿中已有的地址 |
| validate_addressB | 验证地址是否合法、可达 |
| list_packagesC | 查询已保存的包裹模板列表 |
| list_predefined_packagesA | 查询承运商预定义包裹列表。返回按承运商分组的预定义包裹，包含尺寸和重量信息。用户发货时可通过 carrier_package_id 直接引用预定义包裹，无需手动填写尺寸。 |
| create_packageC | 创建包裹模板，方便下次快速使用 |
| list_carriersA | 查询已连接的承运商账户列表 |
| get_service_levelsC | 查询客户生效中的承运商服务级别 |
| list_storesA | 查询已连接的电商店铺列表 |
| get_total_savingsC | 查看使用 ShipSaving 节省的总金额 |
| get_shipping_analysisA | 按时间维度分析运费数据。调用前必须先询问用户选择时间范围，可选值：the_last_7_days（近7天）、the_last_30_days（近30天）、this_month（本月）、last_month（上月）、current_year（今年）、last_year（去年）。 |
| get_wallet_infoA | 查询钱包余额信息 |
| get_transaction_historyC | 查询交易记录 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-order-workflow | 引导完成下单工作流：查询运费 → 创建草稿运单 → 支付 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
Each tool targets a distinct function (order management, shipping, rates, addresses, etc.) with clear descriptions that prevent ambiguity. Even similar concepts like buy_label_from_order vs create_draft_shipment are explicitly differentiated.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_address, get_shipping_rates, list_carriers). No mixing of conventions or vague verbs.
30 tools cover a broad shipping domain (orders, shipments, carriers, payments, analysis). While slightly over the typical range, each tool serves a purpose and the count is justified for the server's scope.
The tool set covers the full lifecycle: order creation, shipment processing, address management, rate comparison, payment, tracking, and analysis. Minor gaps like batch operations are acceptable for a shipping assistant.