What replaces a custom GPT's Actions after it retires

What an Action becomes

Where a connector can run

From the Claude Help Center and OpenAI's help (Wayback copy of 19 October 2026), read 5 November 2026.

Rebuild an Action in six steps

1. List the Actions. In the GPT's editor, open each Action and copy its schema, the operations it calls and how it signs in.
2. Look for a connector. If the service, such as a CRM or a booking system, already offers one for Claude or ChatGPT, use it instead of building your own.
3. Sort each call into read-only or write. Write calls need the most care: who may run them, and whether a person approves each one.
4. Build the server. A developer exposes each operation as a tool on a remote MCP server, with a clear title and description, and moves the key or OAuth sign-in there.
5. Review it before anyone connects it: who runs it, what each tool can reach, and what it does with the data.
6. Add it and test it with three requests the GPT used to handle, then write when to use each tool into the skill that replaces the GPT.

A worked example: a GPT with two Actions

Illustration: a made-up business. An events company of twelve on Claude Team has a "Venue finder" GPT with two Actions: one searches its venue database, the other holds a date in its booking system. Two freelance planners use ChatGPT Pro.

1. Search venues becomes a read-only tool, which can run without asking each time once it's allowed.
2. Hold a date becomes a write tool. Claude asks before each hold, and the freelancers, on ChatGPT Pro, can search but not hold.
3. The Owner adds the connector under Organization settings > Connectors, and each planner connects with their own account.
4. The GPT's instructions become a skill that says to search first and to hold only after the client confirms the date.

The freelancers send a hold request to the office, which runs it in Claude. Nothing posts to the booking system without a person seeing it first.

Share the instructions with the connector

A connector does the calls; the instructions that say when to make them belong in a skill. Put that skill in AI Skill Pod, and everyone on the team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise) from one invite link, free to start. Each person still adds the connector itself in their own AI.

AI Skill Pod is this site's product. Pod pricing: Free up to 3 members and 10 skills; Team $5 per seat a month from 3 seats.

Next step: keep the team on one copy after 11 December

With the Actions rebuilt, the people who used the GPT by link need the new skill and connector. Keep your custom GPT shared after it retires covers telling your team and clients.

Questions

Do custom GPT Actions keep working after 11 December 2026?

No. Custom GPTs stop running then, and OpenAI's migration FAQ says custom actions don't transfer to the plugin a GPT becomes. Each Action has to be rebuilt with a supported connector or a custom MCP server.

How do I turn a GPT Action into an MCP server?

A developer takes the Action's OpenAPI schema and exposes each operation as a tool on a remote MCP server, with a title, a description, an input schema and a read-only or write hint, and moves the API key or OAuth sign-in to the server. Check first whether the service already offers a connector; many do.

Can ChatGPT Pro run a connector that changes data?

OpenAI's help says Pro connects custom MCP servers with read and fetch permissions only, so a tool that creates or changes something isn't expected to run there. On ChatGPT Business and Enterprise an admin or owner adds the connection with full access, and in Claude custom connectors work on every plan.