OpenAI Developers

Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Claude Code. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.

Use when the user explicitly wants a ChatGPT App, Apps SDK project, MCP server plus widget UI, ChatGPT-compatible tool UI, or submission/deployment work for that surface. Build, scaffold, refactor, or troubleshoot those projects from Claude Code, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials.

Use when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.

Use when an OpenAI API request fails or the user asks what an error means, including blocked access to api.openai.com, 401 invalid_api_key, missing OPENAI_API_KEY, 429 insufficient_quota, 429 rate_limit_exceeded, or 403 model_not_found. Classify the failure, name the next step, route credential setup to openai-platform-api-key, and current guidance to openai-docs.

Use whenever the user asks anything about OpenAI products, APIs, models, or SDKs — including factual lookups ("what is the newest model", "does X support Y"), build/coding requests ("write a script using the Responses API", "how do I use the Agents SDK"), and citation requests. Invoke before calling any openaiDeveloperDocs MCP tool.