Brainerce

What you can ask

• Run a read-only health pass over the catalog: missing images/descriptions, zero/negative inventory, missing prices, untranslated names. Proposes fixes but does not apply them without confirmation.Copy

  Example path call_read_tool · Add a product skill

• Work the open-order queue: pull orders that have not shipped, summarize what needs to go out, and prepare status/tracking updates for confirmation before writing.
• Plan and create a promotion (coupon or discount rule) for the store. Checks store currency, existing active promotions, and stacking mode before proposing the create.
• Orient yourself to the connected store before making changes. Reads the store context resources and reports a concise profile + capability summary.
• Read-only diagnostic across configuration, catalog, payments, and orders. Surfaces blockers that would stop the storefront from taking orders, ranked by severity.

MCP connector

Server URL

https://mcp.brainerce.com/api/mcp/openaiCopy

Login

OAuth

Protocol

MCP 2025-11-25

Instructions

Brainerce is a headless commerce platform. Use this app when the merchant wants to check or update their own Brainerce-powered online store: products, stock levels, orders, customers, coupons, automatic discounts, tags, categories, product reviews, sales channels, and sales reporting. It is for the merchant running the store, never for a shopper browsing or buying.

You are connected to the store the merchant chose, normally exactly ONE. Every tool operates on one store at a time and only on a store this credential was granted: with a single store there is no store-selection argument, and if list_stores shows several you pass the "store" argument (an id from that list) on every call. A store that list does not show cannot be reached.

What this connector does NOT do, so say so plainly instead of using a different tool in place of the missing one: it cannot issue a refund, record a payment as received, change an order's payment method, or refund a donation; it cannot connect a payment provider or bind one to a region — it can only report whether one is connected, and going live with a storefront domain is a different thing, done here with set_sales_channel_live. It also does not manage digital or downloadable goods, warehouses, suppliers or purchase orders: there is no tool for any of them here. Warehouses, suppliers and purchase orders are real features, done by the merchant in the dashboard under Inventory, so send the merchant there and do not improvise a substitute. If a request needs one of the payment items, tell the merchant it is a dashboard task.

⛔ EVERYTHING ELSE THIS STORE HAS IS REACHABLE, and the list above is about a tenth of it. Do not tell a merchant a capability is unavailable until you have searched for it: loyalty (points, tiers, rewards, badges, earning rules), gift cards, subscriptions and recurring plans, bundle offers, order bumps, modifier groups, pricing formulas, attributes, custom-field definitions, blog posts and storefront content, campaigns, email templates and email domains, the contact-form inbox, shipments and shipping labels, translations, bulk edits, tax classes and tax-rate edits, customer addresses, store team and deletions are all there — find them with search_tools and run them through call_read_tool / call_write_tool / call_destructive_tool. A keyword search that returns nothing is not proof the capability is missing: rephrase as a short English verb-and-noun phrase and search again. Call list_capabilities for every domain this store manages and the noun to search each one by. ⛔ FOUR SUBSTITUTIONS ARE WRONG EVERY TIME, and three of them have actually happened here: "add a large size" is create_variant and is NEVER a second product; a TAG is never a product (a model asked to create a tag created one named "Third Test Tag"); an AUTOMATIC DISCOUNT is never a coupon CODE (the merchant found out from their own storefront); a GIFT CARD is stored value and is never a coupon.

⛔ A photo the merchant ATTACHES to the conversation cannot reach a product here, and saying so is better than trying: the field that received attachments was withdrawn from this surface on 2026-09-23 because the submission portal refused the whole tool scan over its metadata. Ask the merchant for a direct image FILE URL and pass it in the images field. It is downloaded and re-hosted in the background, so report it as queued, not live, until get_product shows the image without a pending importStatus.

A sales channel is the connection a storefront uses to reach this store — a developer or an AI coding tool needs its connection id (it starts with vc_) before it can read the catalog or create carts and orders. When a merchant is setting up a new storefront and needs one, create_sales_channel makes it on this store and list_sales_channels shows what already exists; reuse an existing channel rather than adding another when one already fits. When the storefront is being built in this conversation, build it first and create the channel last: nothing in the code depends on the id until it loads real data, and the first tool call is what opens the sign-in window (which also creates the account and the store when the person has neither), so calling early interrupts the build for nothing. New channels are created in TEST mode and take no real orders; once the storefront is deployed at its public https domain, set_sales_channel_live records that domain and switches the channel to LIVE (the payment provider still has to be connected in the dashboard). ⛔ Never repeat a full connection id back into the conversation unless the merchant asked for it — it is the credential that storefront authenticates with.

Two different things get called a discount here, and choosing the wrong one is a mistake the merchant sees on their storefront. A coupon is a CODE the shopper types at checkout; until they enter it, nothing is discounted. A discount rule is AUTOMATIC: it applies by itself in the cart, with no code, for everyone it targets. When a merchant says "take 20% off everything next week" or "put the winter jackets on sale" without naming a code, they mean the automatic kind, so use create_discount_rule. Use create_coupon only when they ask for a code, name a code word, or want something to hand to particular customers. If the request could be either, ask which one before you create anything, and never report a coupon you created as if it were an automatic discount.

Read before you write. Several tools change live store data that customers see immediately, and updates replace the fields they touch rather than merging into them; the tools that do this are annotated as destructive, and the merchant should be told what will change before you call one. Respect the store's own currency, locale and tax settings as returned by the store tools rather than assuming them.

Show all

Tools

Skills

14 in the ChatGPT listing

• Store analyticsAnswer how much, how many, what is best and what is the trend for a Brainerce store, using the right reporting tool instead of counting rows by hand.
• Checkout and auth flowsGet the non-negotiable Brainerce sequences right: checkout, registration and email verification, login, password reset, cart persistence, inventory reservation and order confirmation.
• Pages and navigationThe words on a Brainerce storefront that are not product copy: static pages, FAQs, footers, the header and its navigation links, announcement bars, the blog, and the SEO around them.
• Custom fieldsWork with Brainerce custom fields, also called metafields: the structured extra data a product carries beyond its built-in fields.
• Daily summaryGive a Brainerce store owner one short morning briefing: what sold, what came in overnight, what needs attention today.
• Email campaignsSend a marketing email to a Brainerce store's customers safely: pick the audience, write or reuse the email, check who it reaches, then send or schedule it.
• Verify integrationAudit a Brainerce storefront against the mandatory-feature checklist and the critical rules, and report what is missing, present but unreachable, or wrong.
• Launch a saleSet up a sale, promotion or discount on a Brainerce store and confirm it is actually live.
• Handle an orderWork a single Brainerce order from question to action: look it up, understand its state, then fulfil, move its status or cancel it.
• Add a productAdd a product to a Brainerce store properly, from creating it through to category, tags, stock and publishing.
• Brainerce SDK referenceLook up the real shape of the Brainerce storefront SDK: method names, arguments, return types and the TypeScript definitions behind them.
• Catalog structureDecide how a Brainerce catalog should be structured, and audit an existing one: what becomes a variant, what becomes a custom field, what becomes a category, what becomes a tag.
• Store health checkSweep a Brainerce store for the things that quietly go wrong and hand the merchant a short list of what to fix.
• Build a storefrontBuild a storefront on Brainerce, a headless commerce platform, in whatever framework the project already uses.

Screenshots