Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@brainerce/mcp-server show me the checkout business flow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Framework-agnostic domain knowledge for building on Brainerce, a headless commerce platform. This MCP server answers questions an AI coding assistant needs while building or extending a Brainerce-powered storefront — SDK reference, type definitions, business-flow sequencing, critical rules, and a given store's live capabilities.
It does not generate framework boilerplate. Use Next.js, Remix, Vite + React, Vue, Svelte, Astro, SolidStart, or whatever the surrounding project already uses — this server tells the agent what to build correctly, not how to lay out files. For opinionated scaffolding, see the companion create-brainerce-store CLI.
Claude Code (plugin):
claude plugin install brainerce-mcp@claude-plugins-communityAny MCP client (stdio, manual config):
{
"mcpServers": {
"brainerce": {
"command": "npx",
"args": ["-y", "@brainerce/mcp-server"]
}
}
}Related MCP server: Component Library MCP Server
Tool | Purpose |
| Live features configured for a specific store (payment providers, OAuth, discounts, shipping, i18n). Call first — it tells the agent which conditional features to build. |
| Functional coverage checklist — what users must be able to do, not which files to create. Mandatory features must exist even when currently disabled in the store (they auto-hide; owners enable them later). |
| Do's and don'ts that cause production incidents if violated — SDK usage, auth token handling, checkout invariants, i18n, type safety. |
| Non-negotiable ordered SDK call sequences: checkout, auth, password reset, OAuth, order confirmation, cart persistence, inventory reservation. |
| SDK documentation by topic — setup, API usage, best practices. |
| TypeScript types for Product, Cart, Checkout, Order, etc. |
| Short, focused snippets for tricky SDK calls (payment confirmation, reservation countdown, OAuth redirect, variant selection). |
| Live store metadata (display name, currency, language) for a sales channel. |
| Step-by-step integration walkthrough — |
sdk-types — the full Brainerce SDK type surface as a text resource.
create-store — framework-agnostic brief for building a new Brainerce-powered store; instructs the agent to call the knowledge tools above before writing code.
add-feature — focused prompt for adding one feature to an existing Brainerce store.
pnpm build
pnpm start:stdio # stdio transport, for local MCP clients
pnpm start:http # Streamable HTTP + legacy SSE, for remote clients (default port 3100)The HTTP server is a public, unauthenticated documentation oracle by design — everything behind it is public SDK/docs data. It applies allow-listed CORS, per-IP rate limiting, request size caps, and SSE session limits; see src/bin/http.ts for details.
This server serves static SDK documentation and, for the store-scoped tools (get-store-info, get-store-capabilities, get-required-features), reads public store configuration via Brainerce's public API. It does not collect or store conversation data. See brainerce.com/privacy for the full policy.
MIT — see LICENSE.
Get the non-negotiable business flows for a Brainerce store. Returns ordered SDK call sequences for checkout, auth, password reset, OAuth, order confirmation, cart persistence, and inventory reservation. Framework-neutral — no file paths, no framework-specific code. Call this before implementing any of these flows.
Inputs: flow (required).
Get a short, focused TypeScript snippet for a specific Brainerce SDK operation. Framework-neutral — no Next.js file paths, no Tailwind, no framework-specific imports. Use this when you need the exact shape of a tricky SDK call (payment confirmation, reservation countdown, OAuth redirect, variant selection, etc.). For full SDK reference by topic, use get-sdk-docs instead.
Inputs: operation (required).
Get the do's and don'ts for building a Brainerce store. Returns framework-neutral rules that cause production incidents if violated — SDK usage, state management, auth token handling, checkout invariants, i18n, and type safety. Call this before writing SDK code.
Inputs: topics.
Get the Brainerce integration guide for connecting any website to Brainerce. Returns step-by-step instructions with full API endpoints, request/response examples, and code snippets. Use "core" for the main guide (products, cart, checkout, payment, orders), "optional" for extra features (accounts, OAuth, promotions), or "rules" for validation, error codes, and edge cases.
Inputs: part (required).
Get the functional coverage checklist for a Brainerce store. Returns user-capability-level features (what users must be able to do) rather than pages or file paths. Every feature marked mandatory must exist in the finished build, even when the underlying capability is currently disabled — those features auto-hide and store owners enable them later. Pass a salesChannelId to tune the checklist to the live store; without it, returns the generic complete-store checklist.
Inputs: connectionId, salesChannelId.
Get Brainerce SDK documentation for a specific topic. Returns setup instructions, API usage, code examples, and best practices. Start with "setup" or "critical-rules", then request specific topics as needed.
Inputs: topic (required), currency, connectionId, salesChannelId.
Get live store capabilities and configured features for a sales channel. Returns what payment providers, OAuth, shipping, discounts, and other features are set up. Use this to discover what your store supports and what pages/components to build.
Inputs: connectionId, salesChannelId.
Fetch live store information from the Brainerce API using a sales channel ID. Returns the channel display name (what the user sees in their dashboard), parent store name, currency, and language. Use this to personalize the store being built — prefer the channel name for user-facing text since a single Brainerce store can have multiple sales channels.
Inputs: connectionId, salesChannelId.
Get TypeScript type definitions from the Brainerce SDK, segmented by domain. Use this when you need to understand the exact shape of objects like Product, Cart, Checkout, Order, etc.
Inputs: domain (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 9 tools
Each tool targets a unique aspect of Brainerce store integration—business flows, code snippets, rules, guide, features, docs, capabilities, info, types—with no functional overlap.
All tool names follow the exact 'get-<noun-phrase>' pattern using snake_case, ensuring predictable and uniform naming.
9 tools is an ideal scope for a documentation/guidance server, covering all essential information retrieval needs without excess or deficiency.
The tool surface comprehensively covers guidance for building a Brainerce store—flows, rules, features, capabilities, code examples, types—leaving no obvious gaps for its stated purpose.
Serves your design system and coding standards to coding agents, so they stop guessing.
Gives AI agents direct access to your Sanity projects and guidance for working with them
Spree Commerce docs for AI coding agents: build headless B2B and marketplace ecommerce on its APIs.
E-commerce skills for AI agents: feeds, Google Shopping, GA4. Your private Brain when signed in.
