Build with GemBoss.
Everything you need to set up your store, connect your stack, and drive the agent. From first capture to the API and MCP.
Start here.
Getting started
Connect Shopify, point at a reference, and ship your first store.
Capture & compose
How GemBoss captures a brand and composes a fidelity-scored store.
Themes & sections
The section library, and how a theme is assembled and edited.
Experiments (GemX)
Run A/B tests and read conversion analytics from your store.
Integrations
Klaviyo, Judge.me, Recharge, Meta, Google and more.
API & MCP
Drive GemBoss from your own agent over JSON-RPC.
From connected store to first build.
Four steps. The whole loop runs inside GemBoss, and you approve anything that touches the live storefront.
- 1
Connect Shopify
Authorise GemBoss on your store. It reads your catalog and theme, and writes nothing until you approve it.
- 2
Point at a reference, or describe the store
Paste the URL of a store or product page to capture, or just describe what you sell: a skincare store for clean-beauty fans. You can skip straight to generate at any point.
- 3
Set the goal and the audience
Pick what this build is for (higher conversion, stronger brand, a new launch, a seasonal campaign) and who it is for. The goal changes which sections get chosen and how they are ordered.
- 4
Review, then publish
Every build lands as a draft theme you can open, compare and edit. Nothing reaches the live storefront until you publish it.
Drive GemBoss from your own agent.
GemBoss exposes its analytics over the Model Context Protocol, so an agent like Claude can read how your store is actually performing and reason about it. Calls are JSON-RPC 2.0 over HTTPS, authenticated with a bearer key and scoped to a single shop.
What you should know
- Read-only. These tools carry the
workflow:readscope. Nothing here can change or publish your store. - Scoped per shop. A key is bound to the shops it may read. A request for any other shop is rejected.
- Issued on request. There is no self-serve key yet. Ask us and we will issue one, along with the base URL for your workspace.
Available tools
| Tool | What it returns |
|---|---|
gemos.get_metrics | Funnel, conversion rate, AOV, per-section engagement and per-variant CR. Start here for any performance question. |
gemos.get_segment_funnel | The funnel broken down by segment, with sessions reaching each stage. |
gemos.get_source_metrics | Metrics by traffic channel: direct, organic, social, referral. |
gemos.get_device_metrics | Metrics by device: mobile, tablet, desktop. |
gemos.get_visitor_metrics | New versus returning visitors, each with sessions, CR, AOV and profit. |
gemos.get_time_patterns | When visitors shop and convert, by day of week and hour of day (UTC). |
gemos.get_campaign_revenue | Revenue and profit attributed to each UTM campaign, first touch. |
gemos.list_campaigns | The shop's governed campaigns and the state each one is in. |
gemos.get_behavior_signals | Top products viewed per SKU and top on-site search terms. |
gemos.get_market_signals | Competitor price moves and the niche price band for your category. |
gemos.get_recommendations | Ranked CRO hypotheses: what to change, and why. |
gemos.get_tracking_health | Self-audit of the tracking pipeline, flagging gaps and broken stitching. |
gemos.get_store_state | Which theme is live, the latest job, and Shopify connection status. |
Prefer a walkthrough?
Book a demo and we'll show you the whole loop on a store like yours.