The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Goodbarber Public MCP listing page.
44 AI-powered skills to manage your GoodBarber app with any MCP-compatible client — eCommerce, Community, Membership, and CMS.
Listed on Smithery.
These skills connect to the GoodBarber MCP server and give your AI assistant structured workflows to manage your products, orders, customers, promotions, subscriptions, content, analytics, and more — all from a conversational interface.
Skills are instruction files (.md) that teach an AI assistant how to perform specific tasks using your GoodBarber app's API via MCP (Model Context Protocol). Instead of manually calling API tools one by one, a skill orchestrates the full workflow — from data retrieval to formatted report — in a single natural-language request.
For example, asking "Show me my best sellers this month" triggers the shop-best-sellers skill, which automatically fetches your orders and catalog, computes rankings, and returns a formatted report.
The repo is a Claude Code plugin: it ships the GoodBarber MCP server (.mcp.json) and the 44 skills in one package.
Once the plugin is listed in the community marketplace, install it from any session instead:
On the first GoodBarber tool call, Claude Code opens the authorization page: paste your Public API key and validate. Details in SETUP.md.
You need to add the GoodBarber MCP server as a custom connector in your client. The server implements the MCP 2026-07-28 protocol over Streamable HTTP (earlier handshake-era clients still connect). The /mcp/sse path name is historical and kept only for backward compatibility.
MCP Server URLs:
| Setup | URL |
|---|---|
| Single app | https://mcp.goodbarber.dev/mcp/sse |
| Multiple apps | https://mcp.goodbarber.dev/<app_id>/mcp/sse |
Replace <app_id> with your GoodBarber app ID if you manage multiple apps.
Authentication: the GoodBarber MCP server uses a browser-based OAuth flow.
When your MCP client connects to the MCP endpoint, it may open an authorization page on
mcp.goodbarber.dev. On that page, you will be asked to paste your GoodBarber Public API key and validate the authorization. Generate your Public API key from your app's GoodBarber backoffice, on the Public API / MCP server page.Important:
- Do not open the
/authorizeURL manually in your browser.- Start from the MCP client by connecting to the MCP endpoint.
- The client generates the full authorization request parameters automatically (
redirect_uri,client_id,state,code_challenge, etc.).If you open the authorization page manually without those parameters, the authentication will fail.
Claude Desktop (Cowork):
Claude Code (CLI):
Then start a Claude Code session — on the first GoodBarber tool call, the CLI will open the GoodBarber authorization page in your browser. Paste your Public API key there and validate to complete the OAuth flow.
Cursor / VS Code / Windsurf:
Add to your MCP configuration file (.cursor/mcp.json, .vscode/mcp.json, etc.):
The first connection from your client triggers the OAuth flow in your browser — paste your Public API key on the GoodBarber authorization page and validate.
Cline:
Open MCP Servers in Cline, choose "Remote server", transport Streamable HTTP, URL https://mcp.goodbarber.dev/mcp/sse, or add this to cline_mcp_settings.json:
On the first connection Cline opens the GoodBarber authorization page in your browser — paste your Public API token there and validate. No API key in the config, no environment variable. Agents can also follow llms-install.md.
Any other MCP-compatible client:
Point your client to the MCP endpoint above (Streamable HTTP). The GoodBarber MCP server follows the standard MCP protocol and works with any compliant client.
Clone this repo and copy only the skills for your app type:
Note: the examples below use Claude's local skills directory (
~/.claude/skills/). If you use another client, copy the skill folders to the directory expected by that client.
eCommerce app:
Community app:
Membership app:
CMS / Content (any app with content sections):
Tip: CMS skills are cross-cutting — install them alongside any app type that has content sections (articles, agenda, maps, galleries, videos, sounds).
Tip: If your GoodBarber app combines multiple types (e.g. eCommerce + Membership), install skills from both directories.
Note: skill directory names carry their family prefix (
shop-,community-,membership-,cms-) and are unique, so skills from several families can live in the same destination without collisions.
Ask your AI assistant: "What skills do you have?" — it should list the installed GoodBarber skills.
The same package is a Grok Build plugin: .grok-plugin/plugin.json lists the 44 skills and .mcp.json declares the GoodBarber MCP server.
Once the plugin is listed in the xAI plugin marketplace, install it by name instead (grok plugin install goodbarber --trust) or pick it in /marketplace.
On the first GoodBarber tool call, Grok opens the authorization page in your browser: paste your Public API key and validate. Use /mcps to check the connection and /skills to list the 44 skills. Details in SETUP.md.
| Skill | Description |
|---|---|
shop-best-sellers | Rank products by sales volume and revenue over a given period |
shop-catalog-audit | Detect incomplete product sheets (missing images, descriptions, variants) |
shop-low-performers | Identify products with zero or very low sales |
shop-orphan-products | Find products not assigned to any collection |
shop-product-launch | Guided creation of a full product with variants, images, and SEO |
shop-stock-check | Audit stock levels — flag out-of-stock and low-stock items |
shop-reorder-planner | Generate a supplier-ready replenishment queue based on sales velocity |
| Skill | Description |
|---|---|
shop-order-followup | To-do list of orders to process (pending, to ship, to deliver) |
shop-customer-insights | Segment customers into VIP, loyal, dormant, and one-shot profiles |
shop-rfm-segmentation | Recency / Frequency / Monetary customer segmentation |
shop-prospect-nurture | Prioritize prospects and suggest conversion actions |
| Skill | Description |
|---|---|
shop-promo-campaign | Create a promo code + send an announcement push in one workflow |
shop-promo-performance-review | Analyze promo impact: before, during, and after the campaign |
| Skill | Description |
|---|---|
shop-traffic-report | App-level analytics: page views, launches, sessions, platforms |
shop-kpi-monitor | Threshold-based daily/weekly KPI health alerts |
shop-weekly-digest | Automated weekly business recap |
shop-push-broadcast | Compose, preview, schedule, and send a push notification to all customers |
shop-push-targeted | Compose, preview, schedule, and send a push to specific customers or prospects |
| Skill | Description |
|---|---|
community-traffic-report | App analytics: page views, launches, sessions by platform |
community-push-broadcast | Send a push to everyone or to specific community groups |
community-push-targeted | Send a push to specific community users |
community-device-landscape | Platform distribution, top devices, OS versions |
community-weekly-digest | Weekly community activity recap |
| Skill | Description |
|---|---|
membership-subscription-audit | Active vs expired, churn rate, at-risk subscribers, winback opportunities |
membership-expiration-calendar | Upcoming subscription expirations timeline |
membership-longest-subscribers | Identify your most loyal long-term subscribers |
membership-internal-subscription-grant | Create, update, or revoke internal subscriptions |
| Skill | Description |
|---|---|
membership-prospect-followup | Prioritize membership prospects for conversion |
membership-traffic-report | App analytics: page views, launches, sessions by platform |
membership-push-broadcast | Send a push notification to all eligible users |
membership-push-targeted | Send a push to specific users or subscription-status audiences |
membership-device-landscape | Platform distribution, top devices, OS versions |
membership-weekly-digest | Weekly membership business recap |
Skills for managing editorial content — articles, agenda events, map points of interest, photo galleries, videos, and sounds. Work with any GoodBarber app that has CMS content sections.
| Skill | Description |
|---|---|
cms-article-publish | Guided creation of a full article: body paragraphs, category, slug, scheduling, paywall |
cms-event-publish | Create an agenda event with start/end datetime, location, and body content |
cms-place-publish | Create a map point of interest (address + coordinates) with description |
cms-gallery-builder | Batch-upload images into a photo gallery and set titles/status |
cms-article-restructure | Reorder, clean, and fix the body paragraphs of an existing article |
| Skill | Description |
|---|---|
cms-content-audit | Detect incomplete content across all types (no cover, empty body, missing dates/coords) |
cms-draft-review | Surface stale drafts and unfinished content with a recommended next step |
cms-paywall-audit | IAP apps: check premium content has a coherent free preview (accessTier, maxFreeParagraphs) |
cms-stale-content-refresh | Rank aging articles as refresh, re-promote, or retire candidates |
| Skill | Description |
|---|---|
cms-editorial-calendar | Forward view: scheduled publications, upcoming events, expiring content |
cms-weekly-digest | What published this week + what's scheduled next week, by content type |
Note:
weekly-digest,traffic-report,push-broadcast, andpush-targetednames recur across app types. The CMS skills are namespaced by acms-prefix in their frontmatter (e.g.cms-weekly-digest) to avoid collisions — keep them in a separate folder if you install skills from multiple directories.
All skills follow these rules:
These skills work with any MCP-compatible AI client, including:
The skills CLI installs these skills into any supported agent (Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, Gemini CLI, Antigravity, Cline and more) in one command:
Pick the skills you need from the list, or install all 44 with --all. The skills call the GoodBarber MCP server, so connect it first (see "Install the MCP server" above).
Want to add a skill? Create a folder in skills/<app-type>/ with a SKILL.md file. Follow the existing format: YAML frontmatter (name, description, compatibility) + markdown instructions with tool workflow, input/output contracts, and guardrails.
The Unlicense — public domain, no restrictions.