Migrate custom GPT Actions (OpenAPI) to MCP: preview conversions, setup steps, retirement checklist
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Key dates for the retirement of custom GPTs in ChatGPT (December 2026), what migrates automatically and what does not (custom Actions), and a checklist for rebuilding an Action as a remote MCP server.
This tool takes no arguments.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http actionbridge https://actionbridge.tidewellsoftware.com/mcp
Key dates for the retirement of custom GPTs in ChatGPT (December 2026), what migrates automatically and what does not (custom Actions), and a checklist for rebuilding an Action as a remote MCP server.
No arguments.
{
"type": "object",
"additionalProperties": false
}Step-by-step instructions for adding a remote MCP server URL to ChatGPT, Claude, Claude Code, Cursor, VS Code or the MCP Inspector, for a server that uses an access key, no authentication, or per-user OAuth sign-in.
| Argument | Type | Description |
|---|---|---|
| auth | string | access_key: the server expects a Bearer key or OAuth sign-in with that key; none: public server; user_oauth: each user signs in to the underlying API. |
| name | string | Display name for the connector. |
| client | string | |
| server_url* | string | The remote MCP server URL (https://…). |
{
"type": "object",
"required": [
"server_url"
],
"properties": {
"auth": {
"enum": [
"access_key",
"none",
"user_oauth"
],
"type": "string",
"default": "access_key",
"description": "access_key: the server expects a Bearer key or OAuth sign-in with that key; none: public server; user_oauth: each user signs in to the underlying API."
},
"name": {
"type": "string",
"default": "My API",
"description": "Display name for the connector."
},
"client": {
"enum": [
"all",
"chatgpt",
"claude",
"claude-code",
"cursor",
"vscode",
"inspector"
],
"type": "string",
"default": "all"
},
"server_url": {
"type": "string",
"description": "The remote MCP server URL (https://…)."
}
},
"additionalProperties": false
}Validate an OpenAPI 3.0/3.1 schema (JSON or YAML text, for example the schema from a custom GPT Action) and show the MCP tools it converts to: tool names, HTTP method and path, read-only or destructive hints, detected authentication, and any errors or warnings. Use this when someone wants to migrate a custom GPT Action or turn an OpenAPI spec into an MCP server. Nothing is stored and the API is not called.
| Argument | Type | Description |
|---|---|---|
| schema* | string | The complete OpenAPI schema text (JSON or YAML). |
{
"type": "object",
"required": [
"schema"
],
"properties": {
"schema": {
"type": "string",
"maxLength": 1500000,
"description": "The complete OpenAPI schema text (JSON or YAML)."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 8, 2026.