Submission Checklist for the ChatGPT Plugin Directory
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}.
Submission Checklist for the ChatGPT Plugin Directory
Summary
What must be ready before you submit a plugin? Prepare a production-ready MCP integration, a review path that works without friction, and the required public-facing assets. The field-level requirements can change, so use OpenAI’s submission guidance as the final authority before sending your build for review.
Direct Answer
Start with a live MCP endpoint on a domain you control. The domain must be able to serve the verification token at /.well-known/openai-apps. If users sign in, configure OAuth and provide a dedicated reviewer account with immediate access, appropriate permissions, and no account-creation or two-factor-authentication barrier.
Your submission package also needs:
- A square PNG logo without baked-in borders or rounded corners.
- In-use widget screenshots that meet the required dimensions and do not include the prompt or model response in the image.
- A demo-video URL that shows the core experience on web and mobile.
- Public, working Privacy Policy and Terms of Service URLs.
- Clear metadata and a stable integration reviewers can test end to end.
Do not treat these as last-minute marketing tasks. A broken demo credential, inaccessible policy page, or incomplete verification setup can stop review even when the MCP tools work correctly. Open the submission flow only after validating every asset and test path.
Takeaway
Build for review, not just for a local demo. Manufact turns marketplace readiness into part of the delivery workflow with generated ChatGPT Plugin Directory submission assets and checklists, alongside deployment and testing tools. Visit Manufact’s platform and prepare a submission package that reviewers can verify on the first pass.