migrate-oai-app

Convert OpenAI Apps SDK applications to MCP Apps SDK with code mappings.

Updated May 1, 2026
One-click install
npx skills add https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions --skill migrate-oai-app-benjaminmichaelis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oai-app
Source: https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions/tree/main/.claude/skills/migrate-oai-app
Command: npx skills add https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions --skill migrate-oai-app-benjaminmichaelis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides developers with detailed guidance and step-by-step instructions on migrating applications from the OpenAI Apps SDK to the MCP Apps SDK, facilitating a smooth transition between protocols.

Core Features & Use Cases

  • Migration Guidance: Offers comprehensive mapping of server-side and client-side patterns to adapt code and configurations.
  • Reference Resources: Includes links to SDK repositories, documentation, and example projects for practical implementation.
  • Step-by-Step Instructions: Assists developers in reconfiguring CSP, CSP domains, and event handling to fit MCP API paradigms.

Quick Start

Follow the migration steps outlined to convert your existing OpenAI Apps SDK codebase into MCP Apps SDK format, starting with cloning the SDK repository and updating your server and client configurations accordingly.

Frequently Asked Questions about migrate-oai-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an OpenAI Apps SDK application to the MCP Apps SDK?

To migrate an OpenAI Apps SDK application to the MCP Apps SDK, you need to update server-side and client-side code configurations, including CSP domains and event handling, to align with MCP API paradigms.

What is the process for converting OpenAI Apps SDK code to MCP format?

Converting OpenAI Apps SDK code to MCP format involves mapping existing server-side and client-side patterns, reconfiguring CSP domains, and adapting event handling to fit the new MCP API structure.

Do I need to update CSP domains when transitioning from OpenAI Apps SDK to MCP Apps SDK?

Yes, transitioning from OpenAI Apps SDK to MCP Apps SDK requires reconfiguring Content Security Policy (CSP) domains to ensure the application functions correctly within the MCP server and client environment.

Can I use existing OpenAI Apps SDK event handlers directly in an MCP Apps SDK environment?

Existing OpenAI Apps SDK event handlers cannot be used directly in an MCP environment; they must be adapted and reconfigured to fit the MCP API paradigms for proper event handling.

What reference resources are available for migrating OpenAI Apps SDK to MCP?

Migration references include links to SDK repositories, official documentation, and example projects to provide practical implementation guidance for adapting code and configurations to MCP.

Are there limitations to consider when mapping OpenAI Apps SDK patterns to MCP?

When mapping OpenAI Apps SDK patterns to MCP, consider that both server-side and client-side configurations must be comprehensively adapted to ensure a smooth transition without breaking existing event handling and CSP setups.