Build Your Store with Claude
Use the Biokit MCP server to let Claude read your stores and add products for you — no copy-pasting, no manual form-filling. Get set up in two minutes.
Published
Build Your Store with Claude
The Biokit MCP server lets Claude read your stores and add products on your behalf — no copy-pasting, no manual form-filling. This guide walks you through the setup and shows you what you can do once it's running.
This works with Claude Code, Claude Desktop, and any MCP-compatible client. You'll need a Biokit API key — generate one in Settings → API Key.
1. Generate your API key
Go to your Biokit dashboard settings and open the API Key tab.
- Click Generate key.
- Copy the key immediately — it's shown only once.
- Store it somewhere safe (a password manager,
.envfile, or your MCP config).
Treat your API key like a password. Anyone who has it can read and modify your stores.
2. Connect Claude to Biokit
Claude Code (recommended)
Add the following to your project's .mcp.json — or to ~/.claude/mcp.json for global access across all projects:
{
"mcpServers": {
"biokit": {
"url": "https://mcp.biokit.me/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with the key you copied in step 1, then reload MCP with /mcp in Claude Code.
Claude Desktop
Open Settings → Developer → Edit Config and add the same biokit block inside mcpServers. Save and restart Claude Desktop.
Verify the connection
Ask Claude: "List my Biokit stores." If it replies with your store names, you're connected.
3. What you can ask Claude to do
Once connected, Claude has three tools available:
| Tool | What it does |
|---|---|
list_stores | Shows all your stores with IDs and slugs |
get_store | Returns full details for a specific store |
add_product | Creates a new product in a store |
Example prompts
Explore your catalog:
"What stores do I have? Show me the products in my main store."
Add a single product:
"Add a product called 'Brand Strategy Session' to my consulting store — $350, digital, payment link is stripe.com/p/session."
Build a catalog from a description:
"I run a photography preset shop. Add these five presets to my store: Moody Film ($24), Golden Hour ($24), Urban Street ($19), Clean & Bright ($24), B&W Classic ($19). All digital, no payment URLs yet."
4. Build a full store with a single prompt
The most powerful pattern is describing your entire catalog in one go and letting Claude structure it for you.
I'm setting up a Biokit store and need you to add my products.
First, list my stores so I know which store ID to use. Then add the following products to [STORE NAME]:
[PASTE YOUR PRODUCT LIST HERE]
For each product:
- Set the type to "digital", "physical", or "service" based on what it is.
- Write a one-sentence description if I haven't given one.
- Leave paymentUrl empty unless I've provided a link.
- Use USD as the default currency.
Confirm each product as you add it and summarize at the end.
5. Tips for best results
Be specific about the store. If you have multiple stores, name the one you want Claude to use — otherwise it will ask.
Add payment URLs later. You don't need Stripe or Gumroad links ready at catalog-creation time. Add them through the dashboard once the products are live.
Use categories to organise. Tell Claude to group products — "set category to 'presets' for the first three and 'courses' for the rest" — and they'll be filterable in your store.
Bulk imports for large catalogs. For 20+ products, the CSV import workflow is faster. Use Claude to generate the CSV, then import it in one click.
Troubleshooting
"Not authenticated" — Your API key is missing or wrong. Regenerate it in Settings → API Key and update your MCP config.
"API error 404: store not found" — Ask Claude to list your stores first and confirm the store ID it's using.
Claude doesn't see the Biokit tools — Reload MCP with /mcp in Claude Code, or restart Claude Desktop. Check that the url and Authorization header are set correctly in your config.
Changes not showing in the dashboard — Hard-refresh the page. Products are added in real time, but the dashboard may be cached for a few seconds.