Packrift MCP Server

Hosted no-auth MCP for exact-spec packaging search, live price, stock, cart handoff, and no-match.

Tools

Last Updated

Jun 14, 2026

What is the Packrift MCP Server?

The Packrift MCP server gives AI agents structured, permission-aware access to Packrift through the Model Context Protocol. With 16 pre-built actions, agents can read, create, and update Packrift data on behalf of authorized users.

Willow ships the Packrift MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Packrift is being used by every AI agent in your stack.

Tools

google_retail_ai_finder

Controlled Packrift Google Retail / AI Commerce Search sales test. Uses the imported Retail catalog to find likely buyer matches, returns AI_APPROVE-gated cart-handoff candidates, and records low-cap test attribution. Use this for the Gemini/Retail pilot before normal search_products when testing Google Retail search quality.

search_products

Use when the user names a category by keyword (e.g. 'kraft tape', 'bubble mailer', 'starter kit') with no dimensions. For dimension-based fit, prefer find_packaging_for_item. Returns products with price, stock, URL.

get_product

Use after find_packaging_for_item or search_products to pull full detail for a handle: all variants, SKUs, dimensions, weight, stock. Input: handle. Call before building a cart to map qty to the right variant.

get_pricing

Use to confirm live unit price and line total before cart handoff. Required argument: variant_ids as an array of numeric Shopify variant IDs encoded as strings, for example ["53475949216112"]. Optional quantity defaults to 1. Never send variant_ids as numbers. Never cached.

check_inventory

Use to confirm stock before recommending a SKU or building a cart. Required argument: variant_ids as an array of numeric Shopify variant IDs encoded as strings, for example ["53475949216112"]. Never send variant_ids as numbers. Live, never cached.

find_packaging_for_item

Use when the buyer has item dimensions and needs a fitting box or mailer. Required arguments are item_length_in, item_width_in, item_depth_in, item_weight_lb, and use_case (mailer|box|fragile|apparel|ecommerce). Returns up to 5 AI_APPROVE SKUs ranked by fit with price, stock, URL, and cart-continuity fields.

get_shipping_estimate

Use when the buyer asks shipping cost for selected AI_APPROVE variants. Required arguments: destination_postal_code, country (US|CA), and items with variant_id as a numeric Shopify variant ID string plus qty, for example {"variant_id":"53475949216112","qty":1}. Never send variant_id as a number.

get_cart_handoff_candidates

Returns priority AI-approved Packrift SKUs that are ready for MCP cart handoff exploration, including create_cart_url arguments, SKU records, measured product/reorder/quote links, and the required live-confirmation sequence.

create_cart_url

Final checkout handoff after live product, price, inventory, and buyer confirmation. For most agents, use exact AI_APPROVE sku plus quantity. Use items only when you already have variant IDs as strings. Returns a measured Packrift /r/cart URL with MCP attribution and a Shopify cart permalink; it does not place an order.

prepare_purchase_handoff

Preferred exact-SKU purchase prep for agents. Call first with sku, quantity, and buyer_confirmed=false to confirm AI_APPROVE product, live price, and live inventory. Call again with buyer_confirmed=true only after buyer approval; then it returns a measured source-preserving MCP /r/cart URL. It does not place an order.

1–10 of 16 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Packrift MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-packrift": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/packrift"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-packrift": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/packrift"
    }
  }
}

Claude Code

CLI

claude mcp add willow-packrift --transport http https://<org>.mcp-s.com/mcp/mcp/packrift

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/packrift",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Packrift

Willow adds the layer Packrift and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Packrift MCP Server FAQ

What is the Packrift MCP server?

The Packrift MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Packrift data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Packrift MCP server different from the official one?

The official Packrift MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Packrift MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Packrift MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Packrift, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Packrift actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Packrift MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Packrift MCP locally, you'll see it.

What does the Packrift MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Packrift MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.