find_packaging_for_itemLABSCO SUMMARY
It ends at a cart, which is the part most catalog tools skip.
A product search that returns a name and a picture leaves you exactly where you started. Chaining lookup to live price, live stock and a cart handoff means the assistant can answer 'can I get these by Friday and what will they cost' rather than 'here is a box that might suit'. Constraining SKU selection to approved catalog records is the other deliberate choice: it narrows what can be recommended, which is the correct trade when the output is an order.
What it is
A hosted MCP server for packaging procurement. The job it is built around is narrow and concrete: given an item, a SKU or a reorder need, find the right packaging supply and then confirm the things that decide whether you can actually order it — current price, inventory, shipping, and a cart to complete in. It is backed by a live Shopify catalog.
What you get
- Product lookup against the catalog, with SKU selection constrained to approved records rather than free-form matching
- Live price and inventory read from the Shopify Admin API at query time, not from a cached sheet
- Shipping information and a cart handoff, so the answer ends in something orderable instead of a product name
- Reorder flows for supplies you have bought before
- A 15-tool commerce surface, reachable with no buyer-side API key on the hosted endpoint
Requirements
Nothing for the hosted path: add https://mcp.packrift.com/mcp with type http and it works — no key, no account. Clients that only accept local stdio commands can bridge with mcp-remote and still reach the same hosted endpoint. Self-hosting is available for development: pull ghcr.io/packrift/packrift-mcp:latest, which listens on port 8787; SHOPIFY_PACKRIFT_TOKEN is not needed for tool discovery but is required for live catalog, pricing, inventory, shipping and cart calls, and SHOPIFY_STORE_DOMAIN, SHOPIFY_API_VERSION and STOREFRONT_DOMAIN have working defaults. The container uses an in-memory cache and is meant for testing; production stays on the hosted endpoint.
Setup effort
Paste a URL — add the endpoint to your client
USE CASES
01
Finding packaging that fits a specific item
Describe the item and get the matching supply from the catalog, rather than guessing box sizes from a dimension chart.
02
Checking whether you can actually order it now
Confirm live price and inventory before committing, instead of finding out at checkout.
03
Reordering what you bought last time
Work from the SKU you already use and go straight to current price, stock and a cart.
04
Costing a shipment end to end
Pair the packaging price with shipping information in one conversation to see the real per-unit cost.
15 tools
Listed in project docs. Your client may show a different list.
search_productsget_productget_pricingcheck_inventoryget_shipping_estimateget_cart_handoff_candidatescreate_cart_urlprepare_purchase_handoffcompare_alternativespack_calculatorinventory_statusget_reorder_linkget_bulk_quote_linkexplain_no_exact_matchBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
Both documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://mcp.packrift.com/mcpMCP Clients
Any MCP client — remote HTTP
ANY MCP CLIENT — REMOTE HTTP · JSON
{
"mcpServers": {
"packrift": {
"type": "http",
"url": "https://mcp.packrift.com/mcp"
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"packrift": {
"type": "streamableHttp",
"url": "https://mcp.packrift.com/mcp",
"disabled": false,
"timeout": 60
}
}
}
