One server, two assistants: how ChatGPT plugins and Claude connectors fit together

In July 2026 OpenAI renamed ChatGPT apps back to plugins and merged the listing into one directory shared with Codex. The word from 2023 is back, but what sits behind it is different, and it is worth understanding before commissioning any work.

What a plugin is now

A plugin is not a piece of code living inside the assistant. It is your own server, hosted by you, answering the assistant’s requests. The assistant asks which actions are available, calls the one it needs, and gets back an answer made of your data.

The conversation runs on the Model Context Protocol. Anthropic created it, and Claude speaks it natively: a server like that connects to Claude as a connector. OpenAI builds plugin submission on top of it through the Apps SDK.

Why that matters to a budget

From this follows something people often learn late. You need one server. It serves both ChatGPT and Claude, because both platforms speak the same language.

What differs is the packaging: how the plugin is submitted for review, how it is described in the directory, what a reviewer needs to see. That is real work, but it is not a second build. If someone quotes you two budgets, one per platform, it is worth asking why.

What it gives a business

The entry point moves. The customer does not open your site, create an account and learn your interface. They ask in the chat they already had open, and the assistant reaches your service.

That changes who finds you. People meet your product without having searched for it, and without knowing it existed. They described a task, and the assistant offered a way through and carried it out with your hands.

What a plugin does not do

It does not replace a product. If a service has no clear API and no clear set of actions, the plugin will repeat that vagueness, only in a chat window.

It does not put you in the directory on its own. Getting listed means review, a description, and the examples people judge you by against everything similar. That part is closer to working on a product listing than to programming.

And it does not remove support. Assistants change their rules, the protocol grows, the listing needs keeping up.

Where to start

Look at your service and ask one question: which single action would a customer want to take without opening your interface. If the answer comes in a couple of seconds, you have a candidate.

If you want to talk through a specific service, I describe the process on the plugins page.