From blank shop to busy shop
These are the jobs an agent can do today through the shop's MCP connection. Each one calls the same services as the admin screens, with the same rules.
1. Set up
Name the shop, write its design brief, pick a theme, set delivery options, and change settings such as the low-stock threshold.
2. Build
Create pages and blog posts from content blocks: heroes, layouts, product grids, FAQs and animated scenes. Build the menus and import images.
3. Stock
Add products and variants, fill taxonomy attributes, set prices, images and stock, and organise collections.
4. Sell
Set up promotions and discount codes, manage gift cards, and pause or resume subscriptions.
5. Operate
Check the ops inbox, then pack and dispatch with tracking. Approve returns, refund, cancel, resend emails and look up customers.
6. Grow
Sales and traffic over any period, top products, revenue split by sales, donations and subscriptions, Gift Aid totals and what people searched for.
What it looks like
You talk to the assistant you already use. It reads the shop's design brief before it writes anything, so new pages match your brand. It checks before it changes something that matters.
Works with Claude (claude.ai, desktop and Claude Code) and other MCP clients
Connect with your shop's address: no API keys to copy around
Read-only connections for people who only need reports
You
A customer emailed: order 10482 arrived damaged. Refund the mug and say sorry.
orders.get · manageRefunds (dryRun)
Claude, via the Badger MCP server
Order 10482 has a speckled mug at £18.00 and a linen napkin set. A refund of the mug would be £18.00 back to their Visa ending 4417. Shall I go ahead?
You
Go ahead.
Claude, via the Badger MCP server
Done. £18.00 refunded, and the order notes record the reason as "arrived damaged".
Example conversation. The tool calls shown are the real ones the assistant uses.
Guard rails, built in
Letting software act on a live shop needs limits. These are part of the platform, not left to the assistant's good manners.
Your login, your scopes
OAuth 2.1 with PKCE. Each connection is tied to one shop and to read, write or admin scope, so a reporting connection can't change anything.
Previews before money moves
Refunds and cancellations support a dry run that shows exactly what will be refunded, voided or restocked before anything happens.
A refund limit you set
Set the most an AI agent may refund in one go. Anything larger has to be done by a person in the admin.
No double refunds
Every money action carries an idempotency key, so a retry can't pay out twice.
Secrets stay secret
API keys and other secret settings are always redacted. Customer personal data needs write access.
Says what can't be undone
Tools that can't be reversed, such as dispatching an order, say so, so the assistant asks you first.
Proof
This site was built that way
The site you are reading was built through its own MCP connection: the brand, the pages, the menus and the content blocks. So was a 28-page redesign of the Kedos Consulting website, and a complete pitch site for a mountain rescue team with its own shop, donations and news.
A person still decides what goes live. The assistant does the typing.
48
MCP tools today, covering every area of the shop
1
connection per shop, with its own login and scopes
0
API keys to paste: sign in with OAuth
OAuth 2.1
with PKCE and dynamic client registration
All 48 tools
Grouped by job. Read tools look; manage tools change things.
Set-up and brand
getDesignBrief, manageBranding (brief, logo, CSS, theme)
siteConfig, manageSiteConfig
deliveryOptions, manageDeliveryOptions
Catalogue
products, manageProducts
variants, variantGroups
collections, manageCollections
taxonomies, productTaxonomy
stereotypes, inventory, media
Content
pages, managePages (incl. blog posts)
menus, manageMenus
extensions, extensionConfig, manageExtensionConfig
Selling
promotions, managePromotions
giftCards
subscriptions, manageSubscriptions
Operations
opsInbox, orders, customers
manageFulfilment, manageRefunds
manageCancellations, returns, manageReturns
manageOrderEmails, pipelines
Insight
statistics: sales, products, donations, Gift Aid
siteTraffic: views, top pages, searches
Try it on a shop of your own
Start a Lite trial, connect Claude to your shop, and ask it to set up your first products.