Submit plugins

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

Use the plugin submission portal to submit a plugin for review when you're ready to publish it for public use.

If you're migrating an existing Claude Code plugin or connector, first review Submit your Claude Code plugin to OpenAI to see what you need to change before starting the submission.

If the portal returns an error code, use the submission error reference to find the matching requirement.

A plugin can contain skills, MCP servers, or both. You can submit:

• A skills-only plugin that packages reusable workflows.
• A remote MCP-only plugin. Custom UI is optional.
• A plugin that combines a remote MCP server with uploaded or MCP-imported skills.

Submit MCP servers through With MCP using a stable, public HTTPS endpoint. If your MCP server runs locally, deploy it to a public HTTPS URL. If you can't, reach out to your OpenAI contact for local MCP support.

The portal collects listing information, MCP server or package details, skills, starter prompts, test cases, country availability, and policy attestations. Which fields you complete depends on whether the plugin includes skills, a remote MCP server, or both.

For local development, packaging, and marketplace setup, see Build plugins.

For server-backed capabilities, see Build an MCP server.

Before you submit

Submit the remote MCP server, not an existing integration reference

You cannot submit a plugin that references an existing, already-published integration. If your plugin includes an MCP server that already exists in ChatGPT or Codex, submit that server from scratch through the portal as a new MCP-backed plugin submission. The portal scans that MCP server, validates the tool metadata, and uses the submitted server details during review.

Get plugin submission access

You need an organization role with plugin submission write access before you can create or submit plugin drafts. The Platform currently labels this permission Apps Management.

1. Open OpenAI Platform roles settings.
2. Select the organization that owns the plugin.
3. Open the role assigned to the submitter, or create a new role.
4. In the role permissions, set Apps Management to Write.
5. Save the role and assign it to each person who needs to create, edit, or submit plugin drafts.
6. Reload the plugin submission portal.

Organization owners already have these permissions. Non-owner submitters need write access to create or submit drafts, and read access to view drafts and review status.

Verify your developer or business identity

Every public submission must use a verified developer or business identity in the OpenAI Platform. Reviewers use this identity to confirm the submission matches the name, website, support contact, privacy policy, and terms in your public listing.

To verify an identity:

1. Sign in to the OpenAI Platform.
2. Select the organization that will publish the plugin.
3. Open organization settings.
4. Complete individual verification if you will publish under your own name, or business verification if you will publish under a company name.
5. Return to the plugin submission form and select the verified identity in the Developer Identity field.

Reviewers may reject submissions that use an unverified or mismatched publisher identity. See the organization verification requirements for the underlying review rule.

If the Platform shows that the developer or business identity is verified but the plugin submission form does not recognize it, check that you are submitting from the same organization and project where the identity was verified. The submitter also needs Apps Management write access for that organization. Ask an organization owner or admin to update the role assigned to the person submitting, then reload the plugin submission portal.

Prepare required materials

Before opening the form, collect:

Material	What to prepare
Listing details	Plugin name, short description, long description, logo, category, website, support URL, privacy policy URL, and terms URL.
Developer identity	Verified individual or business identity in the OpenAI Platform.
Remote MCP server	Public MCP server URL, domain verification access, authentication details, demo credentials if needed, content security policy, and accurate tool metadata.
Tool annotations	For plugins with remote MCP: readOnlyHint, openWorldHint, and destructiveHint values for every MCP tool.
Skills	For skills plugins: a final skill bundle or a remote MCP server that exposes static skills for Scan Tools to import.
Prompts	Starter prompts that show useful, realistic workflows.
Test cases	Five positive test cases and three negative test cases with clear expected behavior.
Availability	Countries or regions where the plugin should be available.
Release notes	A short summary of what you are submitting and what changed since any prior version.

Create a plugin submission

1. Open the plugin submission portal.
2. Select Create plugin.
3. Choose the submission type:
   • Skills only for a skills-only plugin.
   • With MCP for a remote MCP-only plugin.
   • With MCP for a plugin that combines a remote MCP server with uploaded or MCP-imported skills.

The portal saves the submission as a draft while you complete the form.

Complete the form

Info

Complete the public listing and publisher fields:

• Plugin name: Use the customer-facing product or workflow name.

• Descriptions: Explain what the plugin helps users do. Keep the short description concise and use the long description for workflow details.

• Developer Identity: Select the verified individual or business identity for the publisher.

• Logo and category: Use production-ready brand assets.

• Website, support, privacy, and terms URLs: Use public URLs that match the publisher and disclose relevant data handling.

  

Review your MCP responses against your privacy policy before you submit. Remove unnecessary personal data, auth secrets, debug payloads, internal identifiers, and undisclosed user-related fields from tool responses.

MCP

For submissions with a remote MCP server:

1. Choose the MCP server URL type:
   • Choose Universal when one fixed MCP server URL works for all users and organizations.
   • Choose Template only when OpenAI has approved a workspace-specific URL, such as when each customer has a separate tenant, workspace, or managed MCP endpoint.
2. Enter the required URL:
   • For Universal, enter the production MCP Server URL.
   • For Template, enter both an Example MCP Server URL and a Template MCP Server URL. The example must be a concrete, working endpoint that matches the template and works with the submitted test credentials.
3. Configure authentication and provide reviewer-ready demo credentials if the server requires sign-in.
4. Define a content security policy that allows the exact domains your UI fetches from.
5. Complete domain verification if the portal shows a Domain not verified challenge. Use an HTTPS origin on the MCP host name or a parent host name, and host the exact token at /.well-known/openai-apps-challenge.
6. Select Scan Tools.
7. Review the discovered tools, imported skills, domains, validation output, and tool metadata.
8. Fix server, skill, or metadata issues, deploy the fix, then scan again.

To support workspace domain restrictions for a plugin that uses OAuth, configure the authorization server to advertise a UserInfo Endpoint that returns the user's email claim and email_verified: true. Before submitting, confirm that the provider also advertises and enables the openid and email scopes. You can also return these claims in an ID token, but the UserInfo Endpoint is required for workspace domain restrictions. If the provider doesn't support these requirements, work with the provider to add support. See Support workspace domain restrictions.

Template MCP server URLs

Most plugins should use Universal. Template MCP server URLs are available only in limited cases where different groups of users or data require different MCP server URLs. OpenAI supports template-based URLs only for trusted developers with whom we have an established relationship. If OpenAI has not approved your use of a template URL, submit a universal URL.

In the Template MCP Server URL, use \{name\} placeholders for the parts that a workspace admin configures. Placeholder names must start with a letter, contain only letters, numbers, or underscores, and be unique within the URL. The Example MCP Server URL must replace each placeholder with a real value.

For example:

Example MCP Server URL: https://acme.example.com/mcp
Template MCP Server URL: https://{workspace}.example.com/mcp

The example URL must be publicly accessible during review. Don't enter a placeholder URL in the Example MCP Server URL field. For the complete MCP review requirements, see Template MCP server URLs.

Do not enter an existing integration ID or try to point the portal at an existing published integration. The submission must provide the MCP server URL and review materials directly, even when that server backs an integration already published in ChatGPT or Codex.

Domain verification

Plugins with MCP must verify control of the domain that hosts the server. When the portal shows a domain verification challenge, place the exact verification token at the generated well-known URL: