Headless API and MCP

Use Quickshops as your commerce backend while you own the frontend. Prefer @quickshops/sdk on the server. Pro unlocks API keys, MCP, and Telegram.

Build your own storefront, mobile app, or internal tool while Quickshops runs catalog reads, carts, Stripe Checkout, and subscription portals. Use the TypeScript SDK @quickshops/sdk from your server — keep API keys out of the browser.

Pro unlocks API keys, MCP server access, and Telegram for the store agent. The hosted storefront editor remains available if you want both a default shop and a custom frontend for specific flows.

At a glance

TypeScript SDK + React UI

useStore() on the server; Storefront.* composition primitives from @quickshops/sdk/react use your shadcn theme tokens — never put qk_ keys in the browser.

MCP tools (Pro)

Expose store operations to MCP clients. Available on the Pro plan with OAuth or API key auth.

Secure key management

Create expiring keys on Pro, track last used timestamps, and revoke access instantly from the dashboard.

Documentation

SDK install, one-prompt DIY guide, and REST reference.

Start with the TypeScript SDK (@quickshops/sdk). The REST reference lives under the same developer docs. Default SDK host is https://api.quickshops.app. MCP clients connect at https://mcp.quickshops.app/mcp.

Building with Lovable, v0.dev, or Cursor? Follow the one-prompt storefront guide and the Lovable / v0 integration post. Keep your API key on the server, use the SDK for commerce, and pass custom success/cancel URLs so buyers return to your site after Stripe Checkout.

Common use cases

When the hosted editor is not your frontend but Quickshops should still run commerce.

Custom storefronts

Render your own UI in Next.js, React Native, or any stack while Quickshops owns catalog reads, carts, and Stripe Checkout. Call commerce through @quickshops/sdk on the server. You control design; Quickshops controls commerce logic.

Server-side checkout

Create carts and checkout sessions from your backend with API keys that never ship to the browser. One SDK call to checkoutCreateSession returns the Stripe URL.

Agent and automation tooling

Connect MCP-compatible clients (Claude Desktop, Cursor, or your own agents) to the same API surface for workflow and ops automation alongside human sellers using dashboard chat.

Authentication and safety

Designed for trusted backend environments.

API keys from the dashboard

Issue, rotate, and revoke keys from Settings → API keys on Pro. Keys use the qk_ prefix format.

Per-key rate limits

Production traffic is rate-limited per API key. Responses include x-request-id for debugging support requests.

Server-side only

API keys belong in backend code. Missing or invalid keys return standard authentication errors. Do not embed keys in client bundles or mobile apps without a backend proxy.

Get your first key

Create a Pro account and issue a key from the dashboard.

Open Settings → API keys on Pro to issue your first key. Install @quickshops/sdk — it targets https://api.quickshops.app out of the box.

Need a workflow we do not cover yet? Tell us what you are building. Pair the API with payments docs if you are wiring checkout for the first time.

Explore more

See how this feature fits with the rest of the Quickshops stack.

Try the feature on your own store

Sign up free, connect Stripe, and run your first chat update in minutes.

Get started(opens in a new tab)

No credit card required