Skip to content

Commit 9b95994

Browse files
Polish OpenAI migration reference for readability
Add framing prose to the migration guide to improve navigation: - Expanded intro describing document purpose and how to use it - Added note about features marked "Not yet implemented" - Added brief transition sentences before Server-Side and Client-Side sections Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent d055a5d commit 9b95994

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

docs/migrate_from_openai_apps.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,17 @@ title: Migrate OpenAI App
44

55
# Migrating from OpenAI Apps SDK to MCP Apps SDK
66

7-
This guide helps you migrate from the OpenAI Apps SDK to the MCP Apps SDK (`@modelcontextprotocol/ext-apps`).
7+
This reference maps OpenAI Apps SDK concepts to their MCP Apps SDK (`@modelcontextprotocol/ext-apps`) equivalents. Use the tables below for quick lookup during migration, and refer to the code examples for complete before/after comparisons.
8+
9+
This guide covers server-side changes first (metadata, tools, resources), then client-side changes (setup, context, events).
10+
11+
> [!NOTE]
12+
> Some OpenAI Apps SDK features don't have MCP equivalents yet. These are marked "Not yet implemented" in the tables below.
813
914
## Server-Side
1015

16+
The server-side changes involve updating metadata structure and using helper functions.
17+
1118
### Quick Start Comparison
1219

1320
| OpenAI Apps SDK | MCP Apps SDK |
@@ -190,6 +197,8 @@ function createServer() {
190197

191198
## Client-Side
192199

200+
Client-side migration involves replacing the implicit `window.openai` global with an explicit `App` instance.
201+
193202
### Quick Start Comparison
194203

195204
| OpenAI Apps SDK | MCP Apps SDK |

0 commit comments

Comments
 (0)