I built an MCP server for Shopify and Stripe write operations — the gap nobody filled

Davide Conte — Wed, 18 Mar 2026 01:44:36 +0000

Every existing Shopify MCP server has the same problem: read-only.

You can ask your AI agent to show you orders, products, revenue. But you can't tell it to update a price, bulk-edit inventory, cancel an order, or issue a refund. The moment you need to do something, you're back in the dashboard.

I got tired of it. So I built mcp-ecom-hub.

What it does

npx mcp-ecom-hub

A fully typed MCP server that covers what the others don't:

Shopify — write ops:

shopify_update_product — update title, price, inventory
shopify_bulk_update_prices — update multiple variants at once
shopify_fulfill_order — mark orders as fulfilled
shopify_cancel_order — cancel + refund in one call
shopify_create_discount — generate discount codes

Shopify — read ops:

shopify_get_orders — with filters (status, date, customer)
shopify_get_products — full product + variant details
shopify_get_analytics — revenue, AOV, conversion rate
shopify_get_customers — customer list + LTV

Stripe:

stripe_get_revenue — MRR, ARR, breakdown by period
stripe_list_subscriptions — active subscriptions
stripe_cancel_subscription — with proration handling
stripe_create_coupon — discount codes
stripe_get_payouts — payout history
stripe_refund_payment — issue refunds

Multi-store:

hub_list_stores — all configured stores
hub_get_overview — cross-store revenue summary

The gap it fills

Feature	mcp-ecom-hub	Shopify MCP (official)	pipeboard
Shopify write ops	✅	❌	❌
Bulk price update	✅	❌	❌
Stripe integrated	✅	❌	❌
Subscription mgmt	✅	❌	❌
Multi-store	✅	❌	❌
Self-hosted	✅	❌	❌
Open source	✅	✅	❌

Setup

{
  "mcpServers": {
    "ecom-hub": {
      "command": "npx",
      "args": ["-y", "mcp-ecom-hub"],
      "env": {
        "MCP_ECOM_CONFIG": "/path/to/stores.json"
      }
    }
  }
}

Config file (stores.json):

{
  "stores": [
    {
      "id": "mystore",
      "name": "My Store",
      "shopify": {
        "domain": "mystore.myshopify.com",
        "accessToken": "shpat_xxx"
      },
      "stripe": {
        "secretKey": "sk_live_xxx"
      }
    }
  ],
  "defaultStore": "mystore"
}

Safety first

Destructive operations (cancel, refund) require explicit confirmation:

User: Cancel order #1234 and refund the customer
Agent: I'll cancel order #1234 ($89.00) and issue a full refund. Confirm? [yes/no]
User: yes
Agent: ✅ Order cancelled. Refund of $89.00 issued — arrives in 5-10 days.

No accidental cancellations.

Multi-store

Running an agency with multiple clients? One config, all stores:

User: Show me revenue across all stores this week
Agent: 
  - Store A: €2,340 (12 orders, AOV €195)
  - Store B: €890 (8 orders, AOV €111)
  - Total: €3,230

I built a TypeScript boilerplate for OpenClaw skills — scaffold and publish to ClaWHub in one command

Davide Conte — Wed, 18 Mar 2026 00:45:31 +0000

If you've been building OpenClaw skills, you've probably noticed something: there's no official TypeScript template. Every developer is copy-pasting the same SKILL.md structure, setting up tsconfig, wiring tools — from scratch, every time.

I got tired of it. So I built a scaffold CLI.

What it does

npx openclaw-skill-boilerplate my-skill

One command. You get a complete, publish-ready OpenClaw skill project:

✅ Valid SKILL.md with correct OpenClaw frontmatter
✅ TypeScript strict mode
✅ src/tools.ts + types.ts pattern
✅ {{SKILL_NAME}} placeholder replacement in all templates
✅ GitHub Actions CI (build + typecheck)
✅ ClaWHub publish-ready structure

The problem it solves

OpenClaw's skill spec requires a specific SKILL.md frontmatter format:

---
name: my-skill
description: "What your skill does"
version: 0.1.0
author: your-name
tags:
  - category
triggers:
  - natural language trigger phrase
---

Get it wrong and the skill won't load. Add to that the TypeScript setup, the tools pattern, the package.json bin config — it's 30+ minutes of setup before you write a single line of actual skill logic.

With this boilerplate: 30 seconds.

Project structure

my-skill/
├── SKILL.md           # OpenClaw entrypoint
├── package.json
├── tsconfig.json
└── src/
    ├── index.ts       # Main skill logic
    ├── tools.ts       # Tool definitions
    └── types.ts       # Shared types

Publishing to ClaWHub

Once your skill is ready:

npm run build
npx clawhub@latest publish

That's it.

DEV Community: Davide Conte

I built an MCP server for Shopify and Stripe write operations — the gap nobody filled

What it does

The gap it fills

Setup

Safety first

Multi-store

Links

I built a TypeScript boilerplate for OpenClaw skills — scaffold and publish to ClaWHub in one command

What it does

The problem it solves

Project structure

Publishing to ClaWHub

Links