Your app's MCP server now speaks the latest version of the protocol

Every GoodBarber app comes with its own MCP server. It is the secure doorway that lets an AI assistant, with your permission, read and manage your app: write and schedule articles, update products, check your stats, prepare push notifications. You connect the assistant once, it authenticates through OAuth, and it only ever sees your app.

If you are discovering this, two good starting points: our MCP page explains how to connect an assistant to your app, and this article explains what makes an application MCP server different.

On July 28, 2026, the MCP project published a new revision of the protocol. It is a significant one: it makes connections between agents and servers simpler, faster to route, and more reliable at scale. In short, it prepares MCP for a world where AI agents are not an experiment but a daily tool.

We updated the GoodBarber MCP server to support this new revision. Assistants that already speak it are served in the new dialect. Assistants still on previous versions keep working exactly as before, because the server continues to speak those too. Nobody gets disconnected; nobody has to hurry.

Nothing. Your app's MCP server is hosted, secured, and updated by GoodBarber, like the rest of your app's infrastructure. You did not have to read a specification, update a component, or redeploy anything. The upgrade happened the way infrastructure upgrades always happen at GoodBarber: quietly, while your app kept running.

For you and for your app's users, the change is completely transparent and effortless: no action to take, no interruption, nothing new to learn.

This is the practical meaning of an all-inclusive platform. The protocol moved; your app followed; your week stayed the same. It is also one of the clearest differences between building on an app builder and vibe coding an app yourself: when a standard evolves, someone has to do the migration work, and on a vibe-coded app that someone is you. We took a deep look at this exact question in Vibe coding is magic in the demo. Is your app really production-ready?

While testing the update, we verified by hand which protocol version each AI assistant uses when it connects. Yes, by hand: at GoodBarber a human still reads the code, and a human still reads the logs.

The result surprised us. OpenAI's Codex was already using the brand-new version, two weeks after its release. Claude clients were still connecting with the previous one. No drama there: every AI assistant adopts new protocol versions at its own pace, and both behaviors are perfectly correct. But it is exactly why your app's server speaks several versions at once. Whichever assistant you or your team prefer, today or next year, the connection just works.

Protocols will keep evolving, and quickly: MCP is not even two years old and already on its fifth revision. Our commitment is simple: your app keeps up without you having to think about it.

If you have not tried it yet, connect an AI assistant to your app and see what it can already do for you.

What is MCP (Model Context Protocol)?

MCP is the open standard that lets AI assistants connect to applications securely. Every GoodBarber app includes its own MCP server, so an assistant can read and manage the app with the owner's permission.

Which AI assistants can connect to a GoodBarber app?

Any assistant that supports MCP: Claude, ChatGPT and Codex among them, plus a fast-growing ecosystem of MCP-compatible agents. Each connection is scoped to a single app and secured with OAuth.

Do I need to do anything when the MCP protocol is updated?

No. GoodBarber updates the server for every app at once, and older protocol versions keep working during the transition. The update is transparent for you and for your app's users.

Is an app builder better than vibe coding for keeping an app up to date?

For long-term maintenance, yes: an app builder carries the load for you. With a vibe-coded app, every protocol, SDK, or store-policy change is a migration you own. On GoodBarber, the platform team ships those migrations for every app at once; this MCP update reached every app with zero action from owners.