Our MCP server is now a ChatGPT plugin

GoodBarber, a no-code app builder, is now listed in the ChatGPT plugin directory, allowing users to connect their apps and manage content, catalog, members, and push notifications directly from ChatGPT. The company's MCP server, which supports MCP clients like Claude, ChatGPT, and Codex, remains unchanged server-side; the new listing simplifies the connection process for non-technical users. GoodBarber's tests, including sending a push notification about a spring sale, succeeded from a free ChatGPT account.

GoodBarber is now listed in the ChatGPT plugin directory https://chatgpt.com/plugins/plugin asdk app 6a16d2ac52508191887344ea891be616?q=goodbarber . Find GoodBarber in the directory, connect your app, and run it from the chat: content, catalog, members, push notifications. This post extends the announcement on our blog https://www.goodbarber.com/blog/goodbarber-is-now-in-the-chatgpt-app-directory-a1598/ with the developer view, and it closes a loop we opened when we wrote up how we built that server. One line of context for new readers: GoodBarber is a no-code app builder running since 2011 . Customers configure an app in a web back office; the platform compiles native iOS and Android builds plus a PWA. We built a public MCP server https://www.goodbarber.com/mcp/ so that MCP clients Claude, ChatGPT, Codex, Cursor, n8n and others can operate those apps. Nothing changed server-side. Both paths land on the MCP connection your app already has, scoped to that single app and authorized by you. What changed is the effort to get connected: https://mcp.goodbarber.dev/mcp/sse the /sse is a route name; the server speaks Streamable HTTP . This is also the path for Codex: Settings, Integrations, MCP servers, leave the bearer token field empty and the save opens the OAuth flow in a browser.The step-by-step for both lives on our setup page https://www.goodbarber.com/connect-chatgpt-app/ . If you have read our write-up on building the server, you know the architecture. The short version: mcp policy.verification required: true , so a well-behaved client reads back what it just changed before claiming success.Our own tests, including the “Send my users a push about the spring sale.” example that opens the announcement https://www.goodbarber.com/blog/goodbarber-is-now-in-the-chatgpt-app-directory-a1598/ , ran from a free ChatGPT account through the MCP connection: we drafted the push, confirmed it, and it landed on the test phones. Building the server was engineering. Being found is distribution, and for an agent-facing product the distribution surface is inside the assistant, not on your marketing site. Until now, connecting GoodBarber to ChatGPT meant knowing the endpoint existed, enabling a developer toggle, and pasting a URL. That filters out almost everyone who would benefit. A directory listing replaces all of that with a search box: something a non-technical app owner can actually do, without reading a single setup doc. What we do not control: how the directory surfaces or ranks apps. That side is OpenAI's. For us, building the server turned out to be the easy half. The listing is what puts it in front of the people it was built for.