Packrift MCP Server

Production MCP (Model Context Protocol) server for Packrift exact-spec packaging procurement. Hero use case: find the right packaging supply for a given item, SKU, or reorder need, then confirm live price, inventory, shipping, and cart handoff.

• Stack: Cloudflare Workers, TypeScript (strict), Hono, Zod, Streamable HTTP transport
• Backing: Shopify Admin GraphQL API (2025-04), store packrift.myshopify.com
• Endpoint: POST /mcp, GET /mcp (SSE), GET / and GET /start (MCP start page), GET /.well-known/mcp/server-card.json
• Install guide: see llms-install.md for remote MCP client configuration.
• Discovery gate: product lookup, reorder, quote, and cart handoff flows are constrained to AI-approved Packrift catalog records where SKU selection is involved.

Remote MCP client setup

The public Packrift endpoint is hosted at:

https://mcp.packrift.com/mcp

Fast start page for developers, agents, and directory reviewers:

https://mcp.packrift.com/start

Directory and partner handoffs can use tracked start links without changing the MCP endpoint. Use a lowercase source slug with letters, numbers, and underscores:

https://mcp.packrift.com/r/start/{source}

The start page also renders source-specific copy controls when it receives a source:

https://mcp.packrift.com/start?utm_source={source}

Those handoffs record aggregate install-intent telemetry: /r/config/{source} fetches show up as mcp_tracked_config_fetches, /r/install/{source}/{target} opens show up as mcp_install_intent, and copy controls record mcp_install_copy by source and target so partner and directory handoffs can be evaluated before downstream cart events appear.

Custom partner, campaign, directory, and agent-workflow slugs are allowed without code changes as long as they match ^[a-z0-9_]{2,64}$. Examples: mcpservers_org, agency_partner, browser_agent_demo, newsletter_mcp.

When a directory or agent host wants a source-attributed config file instead of an HTML start page, use:

https://mcp.packrift.com/r/config/{source}

Tracked config fetches are exposed by source in https://mcp.packrift.com/ai/mcp-usage-snapshot.json.

For a target-specific tracked install action, use:

https://mcp.packrift.com/r/install/{source}/{target}

Common targets include generic_streamable_http, stdio_mcp_remote, claude_code, codex, claude_desktop, cursor_windsurf_vscode, and cline.

MCP clients that support remote HTTP or Streamable HTTP servers can add Packrift with:

{
  "mcpServers": {
    "packrift": {
      "type": "http",
      "url": "https://mcp.packrift.com/mcp"
    }
  }
}

Cline users should use the tracked Cline target, which returns Cline-native streamableHttp config:

https://mcp.packrift.com/r/install/cline_mcp_marketplace/cline?format=json

Hosts that only accept local stdio MCP commands can use the tracked stdio_mcp_remote target. It runs npx mcp-remote as a thin bridge and still forwards every call to the hosted Packrift endpoint:

https://mcp.packrift.com/r/install/{source}/stdio_mcp_remote?format=json

Hosted connector and directory listings

Use the hosted endpoint above when possible. It requires no buyer-side API key and exposes the current 15-tool Packrift exact-spec commerce surface.

• Glama hosted connector: https://glama.ai/mcp/connectors/io.github.Packrift/packrift-mcp
• MCP Marketplace listing: https://mcp-marketplace.io/server/io-github-packrift-packrift-mcp
• Official MCP Registry search: https://registry.modelcontextprotocol.io/v0/servers?search=Packrift
• Claude connector submission packet: https://mcp.packrift.com/ai/claude-connector-submission.json
• Agent capture outreach packet: https://mcp.packrift.com/ai/agent-capture-outreach.json
• Source repository: https://github.com/Packrift/packrift-mcp
• Direct Streamable HTTP endpoint: https://mcp.packrift.com/mcp

Glama source listing release notes

The hosted Glama connector should remain the primary Glama traffic target. The separate Glama source server listing can use this repository for release and quality checks, but it should still point users at the hosted no-auth MCP endpoint above.

• Dockerfile starts the Packrift MCP server on PORT=8787.
• glama.json is the source-listing maintainer claim file.
• smithery.yaml gives Glama/Smithery-compatible container metadata with an empty config schema, so source-listing release checks do not infer a required buyer token.
• Running the container without SHOPIFY_PACKRIFT_TOKEN still exposes MCP discovery: tools/list returns the current 15-tool surface and resources/list returns the public AI/MCP resources.
• SHOPIFY_PACKRIFT_TOKEN is not required for MCP discovery, directory scanning, or hosted connector use. It is required only for self-hosted live Shopify-backed catalog, pricing, inventory, shipping, and cart tool calls.
• The source listing should not create a separate Packrift CLI or buyer surface; it should release/sync the existing repository and keep the canonical runtime at https://mcp.packrift.com/mcp.

Container Image

The public hosted endpoint above is the primary integration path and the canonical server.json manifest is remote-only. A container image is still published for local development and environments that explicitly require a self-hosted package-style install surface:

docker pull ghcr.io/packrift/packrift-mcp:latest
docker run --rm -p 8787:8787 \
  -e SHOPIFY_PACKRIFT_TOKEN=<shopify_admin_api_token> \
  ghcr.io/packrift/packrift-mcp:latest

You can also build the image from this repository:

docker build -t packrift-mcp .
docker run --rm -p 8787:8787 \
  -e SHOPIFY_PACKRIFT_TOKEN=<shopify_admin_api_token> \
  packrift-mcp

Optional environment variables:

• PORT defaults to 8787
• SHOPIFY_STORE_DOMAIN defaults to packrift.myshopify.com
• SHOPIFY_API_VERSION defaults to 2025-04
• STOREFRONT_DOMAIN defaults to packrift.com
• SHOPIFY_PACKRIFT_TOKEN is optional for MCP introspection and directory scanning, but required when self-hosting live Shopify-backed catalog, pricing, inventory, shipping, and cart tools

The container uses an in-memory cache instead of Cloudflare KV. It is intended for discovery and client testing; the production server remains the Cloudflare Workers endpoint at https://mcp.packrift.com/mcp.

AI Discovery Surfaces