-
Notifications
You must be signed in to change notification settings - Fork 61
docs: how to migrate from openai apps #260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@modelcontextprotocol/ext-apps
@modelcontextprotocol/server-basic-react
@modelcontextprotocol/server-basic-vanillajs
@modelcontextprotocol/server-budget-allocator
@modelcontextprotocol/server-cohort-heatmap
@modelcontextprotocol/server-customer-segmentation
@modelcontextprotocol/server-scenario-modeler
@modelcontextprotocol/server-system-monitor
@modelcontextprotocol/server-threejs
@modelcontextprotocol/server-wiki-explorer
commit: |
jonathanhefner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Really like the table format!
maybe could link this from #256 wdyt?
I was think about something like that too. Do we want it to be part of that skill (e.g., create a new MCP App derived from an OAI App), or do we want it to be a separate skill (e.g., migrate an OAI App to the MCP App SDK)?
docs/migrate_from_openai_apps.md
Outdated
| | -------------------------------- | -------------------------------------------------- | ------------------------------------------------------ | | ||
| | `window.openai` (auto-available) | `const app = new App({name, version}, {})` | MCP requires explicit instantiation | | ||
| | (implicit) | `await app.connect()` | MCP requires async connection; auto-detects OpenAI env | | ||
| | — | `await app.connect(new OpenAITransport())` | Force OpenAI mode explicitly | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noting that this doesn't exist yet (see #172).
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
… into ochafik/docs-migrate-from-openai
…/modelcontextprotocol/ext-apps into ochafik/docs-migrate-from-openai
- Remove AGENTS.md reference to migration guide - Add note that OpenAITransport is not yet available (PR #172) - Remove unnecessary note about return type ordering
|
Addressed the review comments in 9bbd279:
Regarding the skill integration question: I think a separate "Migrate OAI App" skill makes more sense - it's a distinct workflow from creating a new app from scratch, and keeps the concerns separated. But open to either approach! |
|
FYI I think docs pointing to the plugins is a great idea. Most folks will probably be vibe coding apps by end of Q1, let's be honest. |
@jonathanhefner maybe could link this from #256 wdyt?