Storefront MCP

Every Jumpseller store now exposes a public MCP endpoint that AI agents can use to browse your catalog, search for products, and generate direct buy links — all without authentication.

This is the storefront counterpart to the Admin MCP Server. While the Admin MCP requires authentication and lets you manage your store, the Storefront MCP is open to the public and provides read-only access to the same information a visitor sees on your website.

Why Does This Matter?

AI agents are increasingly how people discover and buy products. With the Storefront MCP, your store is ready for this shift:

• AI shopping assistants can search your products, compare prices, and send customers a direct buy link
• Chatbots on your site or third-party platforms can answer product questions with live data
• AI-powered product recommendations can pull your real catalog instead of relying on stale feeds
• Search engines and AI aggregators can discover your MCP endpoint via llms.txt and .well-known/mcp.json

Endpoint

The Storefront MCP is available on every store at:

POST https://your-store.com/api/mcp

Replace your-store.com with your actual store domain (custom domain or yourstore.jumpseller.com).

Transport: Streamable HTTP (JSON-RPC 2.0 over POST). Stateless — each request is independent.

Authentication: None required. This is a public endpoint.

Discoverability

AI agents and crawlers can discover the MCP endpoint automatically through two standard files:

• /api/mcp/llms.txt — Human-readable description of the MCP server and its tools
• /api/mcp/.well-known/mcp.json — Machine-readable MCP discovery metadata

Available Tools

The Storefront MCP provides 6 read-only tools:

What Data Is Returned?

Products include: name, description (plain text), price, compare-at price, brand, SKU, stock availability, images, variants with per-variant pricing and buy links, categories, permalink, and direct URLs for add-to-cart and buy-now.

Categories include: name, description, permalink, URL, images, page title, and meta description.

Store info includes: name, description, country, currency, URL, and logo.

Only available products are returned. Disabled or out-of-stock-hidden products are never exposed. Sensitive merchant data (costs, margins, internal settings) is never included.

Example: Searching for Products

Send a JSON-RPC request to your store’s MCP endpoint:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "search_products",
    "arguments": {
      "query": "summer dress",
      "limit": 5
    }
  },
  "id": 1
}

The response includes matching products with names, prices, images, and direct buy links.

Example: Getting a Product

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_product",
    "arguments": {
      "permalink": "summer-dress-blue"
    }
  },
  "id": 1
}

Rate Limits

The Storefront MCP has two rate limits to ensure fair usage:

• 50 requests per minute per IP address (across all tools)
• 10 searches per minute per store (for search_products only)

If you exceed these limits, you’ll receive an error response. Wait a minute and try again.

Connecting an AI Agent

Any MCP-compatible client can connect to your store’s Storefront MCP. Here’s an example configuration:

{
  "mcpServers": {
    "my-store": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://your-store.com/api/mcp"
      ]
    }
  }
}

No authentication headers are needed — just point the client to your store’s /api/mcp endpoint.

Storefront MCP vs Admin MCP

Coming Soon

We’re working on extending the Storefront MCP with checkout and payment tools, so AI agents will be able to guide customers through the full purchase flow — from product discovery to completed order.

Privacy and Security

The Storefront MCP only exposes data that is already publicly visible on your store’s website:

• Product names, descriptions, prices, and images
• Category names and descriptions
• Store name, country, and currency

It does not expose:

• Customer data
• Order information
• Product costs or margins
• Internal settings or API tokens
• Email addresses