# Quickbutik MCP connector The Quickbutik connector brings your store's orders, products, categories, shipping and payment methods into Elaichi, so Claude, ChatGPT, Cursor or the Elaichi Agent can list, create and update them inside each person's own access. Source: https://elaichi.ai/connectors/quickbutik/ ## Facts | | | | --- | --- | | Application | Quickbutik | | Category | Ecommerce | | AI tools | 20 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Quickbutik is connected - Show me today's unpaid Quickbutik orders and their shipping methods. - Create a Summer sale category and add these five products to it. - Cut prices on every Outlet category product by 20 percent. ## Connect Quickbutik in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Quickbutik. 2. Optionally set Share with, then press Connect. 3. Paste a Quickbutik API key. One person generates a token in Quickbutik and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Quickbutik tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Quickbutik MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Quickbutik MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Quickbutik MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Quickbutik to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Quickbutik tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Quickbutik through Elaichi ### See today's orders without opening the admin Store operations. Ask for this morning's Quickbutik orders, which ones are still unpaid and which shipping method each shopper chose, and get a plain answer in the chat you already have open. ### Change prices across a whole category Merchandising. Pull every product in a Quickbutik category and push a new price or description to all of them in one bulk update instead of editing each product page. ### Answer a shopper while they wait Customer service. Look up a customer's Quickbutik order while they are on the phone, check how they paid and how it ships, and give them a straight answer. ### Move packed orders on in bulk Fulfillment. Once the day's parcels are packed, update the status on the whole batch of Quickbutik orders in one change rather than clicking through them one at a time. ### Set up a campaign category and tracking Marketing. Create a seasonal Quickbutik category, add the launch products to it, and add or update the storefront script for the campaign's tracking pixel. ### Check orders against payouts by payment method Finance. List the month's Quickbutik orders grouped by payment method and compare the totals with what each provider paid out. ## Frequently asked questions ### How do I connect Quickbutik to Claude? Connect Quickbutik in Elaichi first, which means pasting the API key from your Quickbutik store settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and your Quickbutik orders and products are available in Claude. ### Does Quickbutik work with ChatGPT and Cursor as well as Claude? Yes. Once Quickbutik is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Quickbutik once and every client gets it. ### What can an AI agent actually do with my Quickbutik data? An agent can list your Quickbutik orders, products, categories, shipping methods and payment methods, and answer questions about them in plain language. It can create products, categories and orders, update products and orders in bulk, and manage the scripts on your storefront. Short, concrete asks work best, such as asking for today's unpaid orders rather than a long paragraph. ### Does connecting Quickbutik give the AI my whole store? No. The agent works through the API key you connected, so it can only reach what that Quickbutik key allows. Elaichi can narrow that further, for example limiting a team to reading orders, and it never widens it beyond what Quickbutik itself grants. ### Can my team share one Quickbutik connection? Yes. One person connects Quickbutik with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a product or updated an order. ### Can I stop an agent from deleting or changing things in Quickbutik? Yes. Restrictions in Elaichi work per action, so you can allow listing Quickbutik orders and products while blocking bulk deletes or updates. A restricted action is never shown to the AI client at all, so no prompt, however worded, can reach it. ### What happens to a Quickbutik connection when someone leaves? Offboarding a person in Elaichi ends their access to Quickbutik at once, in every client they used. A shared Quickbutik connection keeps working for everyone else on the team. If you want to remove Quickbutik entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client. ### Does the Quickbutik MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. Quickbutik is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ## All 20 Quickbutik tools Every tool below is callable through https://api.elaichi.ai/mcp once Quickbutik is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Quickbutik settings preorders** (List). List the preorder options configured for the quickbutik store. Options can be assigned to products and variants to signal pre-order availability and estimated delivery windows. Returns: id, attributes. - **List all Quickbutik scripts** (List). List Quickbutik storefront scripts, or pass the optional id filter to fetch a single one. Returns a single script record when id is given, otherwise an array of records, each including its string id; remaining fields are defined by the upstream Script schema the docs reference by $ref. Max 500 per page. - **Create a Quickbutik script** (Create). Create a new Quickbutik storefront script. Returns the created script record including its string id, with the remaining fields defined by the upstream Script schema the docs reference by $ref. Required: name, content. - **Update a Quickbutik script by ID** (Update). Update an existing Quickbutik storefront script by id, or create one with a specific id. Returns the updated script record including its string id, with the remaining fields defined by the upstream Script schema the docs reference by $ref. Required: id. - **Delete a Quickbutik script by ID** (Delete). Delete a Quickbutik storefront script by id. Returns a generic success acknowledgement — the upstream SuccessResponse schema, whose fields the Quickbutik docs do not enumerate. Required: id. - **List all Quickbutik orders** (List). List Quickbutik orders with optional search by customer name, email or order ID, plus date/status filtering and sorting. Returns: name, in, schema. Max 1000 per page. - **Create a Quickbutik order** (Create). Create one or more Quickbutik orders with customer, payment, and product details; new orders are always set to status unpaid. Returns a per-order results object keyed dynamically (create_1, create_2, …). - **Quickbutik orders bulk update** (Update). Update one or more existing Quickbutik orders — change status, products, customer, payment, shipping, discounts, or metadata. Returns a per-order results object. Status options: paid, done, cancelled, unpaid. - **List all Quickbutik products** (List). List Quickbutik products with optional filters for product IDs, SKUs, search text, categories, visibility, gift cards, and modification date, with sorting. Returns product records including id, sku, title, price, qty, and variants. Note: the response shape varies — a direct array when the search parameter is used, otherwise a product wrapper or a single object when fetching by product_id or sku. - **Create a Quickbutik product** (Create). Create and add a product to the Quickbutik store by sending a product payload as JSON. Returns the created product record including id, sku, title, price, qty, and variants. The request body follows the ProductCreate schema documented in the Quickbutik API reference. Required: title. - **Quickbutik products bulk update** (Update). Update products in the Quickbutik store by sending an array of update objects as JSON; each product is identified by product_id or variant_id, or directly by SKU/article number when unique. Returns the updated product record including id, sku, title, price, qty, and variants. - **Quickbutik products bulk delete** (Delete). Permanently delete a product from the Quickbutik store. This operation is non-reversible. Returns a results confirmation object. Required: product_id. - **List all Quickbutik products counts** (List). Count the total number of products in quickbutik. Returns the total product count as count. This endpoint takes no parameters. - **List all Quickbutik categories** (List). List Quickbutik store categories, or pass category_id to fetch a specific category. Returns category records identified by id; remaining record fields are defined upstream in Quickbutik. Max 500 per page. - **Create a Quickbutik category** (Create). Create a new product category in Quickbutik. Returns the created category record, including its id and the category attributes defined by the upstream category schema. Required: name. - **List all Quickbutik paymentmethods** (List). List the payment methods configured for the QuickButik store. Returns the store's payment method records with fields defined upstream. Max 500 per page. - **List all Quickbutik shippingmethods** (List). List shipping methods configured for a Quickbutik store. Returns: shipping_id, name, price. Optionally pass shipping_id to fetch a single specific method. Max 500 per page. - **Get single Quickbutik metadatum by ID** (Get). Get the metadata stored for a selected scope and id in Quickbutik. Returns the metadata payload for that record; the upstream documentation does not enumerate the response fields. Required: id, scope. - **Create a Quickbutik metadatum** (Create). Create metadata for a selected scope and metadata id in Quickbutik by adding a metadata payload to that record. Returns a success confirmation only; the upstream documentation documents no response body fields. Required: scope, metadata_id. - **Update a Quickbutik metadatum by ID** (Update). Update the metadata for a selected scope and id in Quickbutik; sending an empty value deletes the corresponding metadata entry. Returns a success confirmation only; the upstream documentation documents no response body fields. Required: id, scope.