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 and preview it privately before it goes live, 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. Mention products in the text so names and prices stay current. Build menus, including mega menus with headed columns, and import images.
3. Stock
Add products and variants, fill taxonomy attributes, set prices, images and stock, and organise collections. Make photos shoppers can buy from, and set up print-on-demand products (early access).
4. Sell
Set up promotions with limits, draft and schedule email campaigns, list products on eBay and Google Shopping, and manage subscriptions.
5. Operate
Check the ops inbox, then pack and dispatch with tracking. Approve returns, refund and cancel, and run the table bookings and appointments diary. Send it a photo of a paper floor plan and it places the restaurant's tables on the room plan.
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
Sign in with your Badger account and choose the shop: 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 first
Refunds and cancellations support a dry run that shows exactly what will be refunded, voided or restocked before anything happens. A new theme, brief or stylesheet can go to a private preview link for you to check before it's published.
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.
83
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 83 tools
Grouped by job. Read tools look; manage tools change things. Tools for restaurants, appointments, marketplaces, subscriptions and print on demand appear only once your shop uses them, so your assistant sees the tools your shop can use.
Set-up, brand and content
getDesignBrief, manageBranding (brief, logo, CSS, theme, private preview)
siteConfig, manageSiteConfig, siteText, manageSiteText
media, manageMedia
pages, managePages (incl. blog posts), menus, manageMenus
extensions, extensionConfig, manageExtensionConfig
Catalogue
products, manageProducts (incl. event tickets)
variants, manageVariants, variantGroups, manageVariantGroups
collections, manageCollections, stereotypes, manageStereotypes
taxonomies, manageTaxonomies, productTaxonomy, manageProductTaxonomy
merchandisingTrees, manageMerchandisingTrees (categories)
shoppableImages, manageShoppableImages (photos to buy from)
Selling and marketing
promotions, managePromotions, giftCards
subscriptions, manageSubscriptions, subscriptionPrices, manageSubscriptionPrices
campaigns, manageCampaigns (email campaigns)
channels, manageChannels (eBay and Google Shopping)
contacts, contactRequests, legalDocuments
Orders and fulfilment
opsInbox, orders, customers
manageFulfilment, manageRefunds
manageCancellations, returns, manageReturns
shipments, manageShipments (parcel labels)
manageOrderEmails, pipelines, managePipelines
podCatalogue, managePodProducts (print on demand)
Stores, events and bookings
locations, manageLocations (hours, closures, limits)
inventory, manageInventory (per location)
deliveryOptions, manageDeliveryOptions, tickets
diningRoom, reservations, manageReservations, tableService, modifierGroups, manageModifierGroups
appointments, manageAppointments
Search and insight
statistics: sales, products, donations, Gift Aid
siteTraffic: views, top pages, searches
productRanking, manageProductRanking
synonyms, manageSynonyms
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.