Three articles showed how GoodBarber's MCP server works for creators. This one is for the people building on top of it.
If you're catching up, the server launched for the shop, then reached your content, then push notifications.
The shift: GoodBarber is now an addressable tool for AI agents
For fifteen years, software has been something humans operate through a screen. Agents change that. The question every platform faces now is simple: when your users reach for an AI assistant to get things done, does your product disappear behind the agent, or does it become the thing the agent drives?
We chose the second. The MCP server makes GoodBarber a first-class tool that any compliant AI agent can discover, call, and verify. You bring your own agent — Claude, Cursor, or anything that speaks the protocol — and GoodBarber exposes a structured, authenticated set of operations it can act on. That's not a shortcut on top of the product. It's the product, made drivable.
What the server exposes — and what it doesn't
Let's be precise, because precision is what a builder needs. The MCP server drives the operational surface of your app:
Shop — products, variants, options, collections, media, orders, promo codes.Content (CMS) — articles, agenda events, map points, photo galleries, videos, audio.Members — subscriptions, prospects, internal grants.Community — groups and audiences.Communication — broadcast and targeted push, with scheduling and tap destinations.What it does not touch: your app's design, navigation, and structure. Those stay in the GoodBarber back office, where they're meant to be crafted, not generated. The server moves content and business data — not your brand. For an agency, that line matters: you can let an agent run a client's catalog or editorial calendar without any risk to the design you shipped.
44 open skills — the orchestration layer
Raw tools are powerful but low-level. A real workflow — "launch a full product with variants, images, and a spec sheet" — is a dozen tool calls in the right order, with checks at each step. That's what skills are for.
We publish 44 skills, open source, at github.com/goodbarber/goodbarber-skills. A skill is a Markdown instruction file that teaches your agent how to run a complete workflow — discovery, dry-run preview, mutation, then verification — from a single natural-language request. They're grouped by app type:
eCommerce (18) — product-launch, catalog-audit, stock-check, reorder-planner, best-sellers, promo-campaign, customer-insights, rfm-segmentation, and more.Membership (10) — subscription-audit, expiration-calendar, longest-subscribers, prospect-followup, and more.CMS (11) — article-publish, event-publish, place-publish, gallery-builder, editorial-calendar, content-audit, and more.Community (5) — push-broadcast, push-targeted, weekly-digest, and more.Two things to know as a builder. First, they're safe by design: product-launch runs dry-run first — it resolves your collections and tags, shows you exactly what it will create, waits for confirmation, then verifies every mutation with a read-back. No half-created products in production. Second, they're yours to fork: they're plain `.md` files. Copy the ones you need into your agent's skills directory, edit the workflow, write your own. They're a starting point, not a black box.
Works with Claude Code, Cursor, and any MCP client
The server speaks standard MCP over SSE. Setup is a one-liner.
Claude Code:
claude mcp add goodbarber --transport sse https://mcp.goodbarber.dev/mcp/sseCursor / VS Code / Windsurf — add to .cursor/mcp.json:
{ "mcpServers": { "goodbarber": { "url": "https://mcp.goodbarber.dev/mcp/sse" } } }First connection opens an OAuth page; you paste your Public API key (generated from your app's Public API / MCP server page) and you're in. No local install, no scripts to maintain.
Here's what a real session looks like in Claude Code — one prompt, and the agent discovers, acts, and verifies:
> Add a product "Trail Map Poster" at €24 in the "Prints" collection, with A2 and A3 sizes. ● shop_list_collections → "Prints" found (id 4821) ● shop_create_product → "Trail Map Poster" created (id 90412) ● shop_create_option (Size) → values: A2, A3 ● shop_create_variant ×2 → A2 €24 · A3 €18 ● shop_get_product (90412) → verified: 2 variants, status published Done. "Trail Map Poster" is live with 2 variants, verified.That discover → act → verify loop is baked into every skill: the agent resolves real IDs first, makes the change, then reads it back to confirm. Nothing is assumed.
For agencies and resellers: one agent, every client app
This is the part built for the reseller program. The server takes an app ID in the URL:
https://mcp.goodbarber.dev/{app_id}/mcp/ssePoint your agent at a specific client's app, run an audit skill across the whole catalog, generate a month of editorial calendar, prep a promo campaign — then move to the next app, same workflow. The skills are reusable across every app you manage. Your agency's playbook becomes a folder of skills.
Distribution and the bigger picture
The server is listed on mcpservers.org, the public MCP directory. It lives in the ecosystem where agents and builders look for tools — discoverable next to every other server worth connecting.
The first three articles were about removing friction for one person. This is about something structural: GoodBarber is now a tool agents can build on. As the models get better at planning multi-step work, the same connection you set up today gets more capable — with nothing to update on your side.
If you build with AI, this is your invitation: connect the server, clone the 44 skills, and orchestrate.
FAQ
Does the MCP server change my app's design? No. It drives content and business operations — shop, CMS, members, push. Design and navigation stay in the GoodBarber back office.
Which clients work? Any MCP-compliant client: Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and others.
Can I manage several client apps? Yes — use the {app_id}/mcp/sse endpoint and reuse the same skills across every app.
Are the skills open source? Yes, 44 of them at github.com/goodbarber/goodbarber-skills. Fork and adapt them.