GoodBarber MCP server
online · 100% uptimedev.goodbarber/goodbarber-public-mcp·v1.3.0·3 starsNo-code app builder: manage your GoodBarber app, shop, community, bookings, content. MCP 2026-07-28.
3 stars
Reviews
Write oneNobody has reviewed GoodBarber yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
GoodBarber tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 363ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 25 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How GoodBarber compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 434 ms
- faster than 38% of 30,027 servers
- GitHub stars
- 3
- more than 80% of 28,706 servers
Release history: 2 versions in the registry since 2026-09-07, latest 2026-10-07, typically one every 30 days.
Install GoodBarber in Claude Code, Cursor or VS Code
claude mcp add --transport http goodbarber-public-mcp https://mcp.goodbarber.dev/mcp/sse
What the publisher says
From the GoodBarber repository's README, as published. We do not edit it. Read it on GitHub
GoodBarber Skills
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.
What are Skills?
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.
Quick Start
Option A — Install as a Claude Code plugin
The repo is a Claude Code plugin: it ships the GoodBarber MCP server (.mcp.json) and the 44 skills in one package.
git clone https://github.com/goodbarber/goodbarber-skills.git
claude --plugin-dir ./goodbarber-skillsOnce the plugin is listed in the community marketplace, install it from any session instead:
/plugin marketplace add anthropics/claude-plugins-community
/plugin install goodbarber@claude-communityOn the first GoodBarber tool call, Claude Code opens the authorization page: paste your Public API key and validate. Details in SETUP.md.
Option B — Manual setup (any MCP client)
1. Connect the GoodBarber MCP
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:
Replace 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 /authorize URL manually in your browser.
- Start from the MCP client by connecting to the MCP endpoint.
- The client generates the full authorization request parameters automatically (redirecturi, clientid, state, code_challenge, etc.).
If you open the authorization page manually without those parameters, the authentication will fail.
Claude Desktop (Cowork):
- Open Settings > Connectors
- Click Add custom connector
- Enter the MCP server URL above
- The connector opens the GoodBarber authorization page — paste your Public API key there and validate
Claude Code (CLI):
# Single app
claude mcp add goodbarber --transport http https://mcp.goodbarber.dev/mcp/sse
# Multiple apps
claude mcp add goodbarber --transport http https://mcp.goodbarber.dev/<app_id>/mcp/sseThen 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.):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
GoodBarber: common questions
- Is GoodBarber MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the GoodBarber safety report
- How do I install GoodBarber?
- It runs remotely at mcp.goodbarber.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does GoodBarber need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is GoodBarber maintained?
- The last commit was 45 days ago (2026-09-21). The latest release is v1.3.0.
- Is GoodBarber up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does GoodBarber compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 434 ms (faster than 38% of 30,027 servers). Full comparison.