Quickshops implements the Model Context Protocol (MCP), which means every operation available through the REST API is also available as a structured tool that any MCP-compatible AI agent can call. You can connect Claude Desktop, Cursor, or your own custom LLM agent to your store and let it perform real actions — listing products, building a cart, or generating a checkout URL — without writing any integration code yourself.Documentation Index
Fetch the complete documentation index at: https://docs.quickshops.app/llms.txt
Use this file to discover all available pages before exploring further.
How it works
The MCP server runs alongside the REST API and automatically generates one tool per API route. Tool names are derived directly from the HTTP method and path, so the mapping is always predictable:| REST route | MCP tool name |
|---|---|
GET /v1/products | get_products |
POST /v1/cart | post_cart |
POST /v1/cart/:cartId/lines | post_cart_cartId_lines |
POST /v1/checkout/session | post_checkout_session |
Transport
The MCP server uses Streamable HTTP transport — MCP over HTTP with SSE for server-to-client notifications. Three endpoints handle the full session lifecycle:| Method | Path | Purpose |
|---|---|---|
POST | /mcp | Initialize a session or dispatch a tool call |
GET | /mcp | SSE stream for server notifications |
DELETE | /mcp | Terminate a session |
mcp-session-id header, which is assigned during the initialize handshake.
Authentication
Authentication uses the samex-api-key header as the REST API. Pass your headless API key with every request:
401 immediately.
MCP server endpoint
Connect your AI client
Step-by-step instructions for Claude Desktop, Cursor, and custom MCP clients.
REST API reference
Explore the underlying REST endpoints that every MCP tool maps to.