Stores & marketplaces

ChatGPT Directory (apps and plugins)

Public directory of apps and plugins inside ChatGPT. Needs a plugin and a review.

Visit developers.openai.com
Cost
Free

No listing fee found in the docs checked. Plugins go through a public review. Check current terms.

Verdict
slow burn

Lets people use your product from inside ChatGPT. It requires building a plugin or MCP server and passing review, and the directory is still young.

Difficulty
Hard

Gatekept or reviewed, or needs an existing audience or reviews first.

Effort
High

About 10 or more hours a month.

First result
1 to 3 months, including review

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Products with an API that answers questions or takes actions people ask an assistant for.

Not for

Products with no API or tool surface.

Pros

  • Use inside ChatGPT
  • Early directory with room to stand out

Cons

  • Must build a plugin and pass review
  • Young and changing

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

OpenAI's developer documentation describes publishing plugins to the "ChatGPT Directory," with a public review for remote MCP servers and optional UI. A listed plugin lets ChatGPT users use your product inside their conversations. The directory is young, the rules are still evolving, and you need to build a plugin before you can list.

02Cost and what you actually pay for

No listing fee was found in the documentation checked. Your cost is building the plugin or MCP server, passing review and keeping it working. Check current terms.

03Is it right for you?

It fits products with an API that answers questions or takes actions people would ask an assistant for, such as search, booking, data lookup or content creation. It fits poorly for products with no API. If your API is unstable, wait.

04Before you start

  • Read the Apps SDK documentation, the plugin guidelines and the review requirements on developers.openai.com.
  • A remote MCP server or plugin, with authentication that protects users' data.
  • A privacy policy and support contact.

05Step-by-step: how to distribute here

  1. Build the plugin using the Apps SDK or an MCP server, following the docs.
  2. Test it with real prompts users would type.
  3. Prepare the server for public review, as the documentation describes.
  4. Submit it to the directory and fix any review findings.
  5. Tell your users how to find and enable it.
  6. Keep it updated as the platform changes.

06What to post or submit

Plugin description:

[Product] in ChatGPT: ask it to [action], e.g. "[example prompt]". Requires a [product] account: [yes/no].

07Common mistakes and do-nots

  • Do not request access to data you do not need.
  • Do not let actions run without user confirmation where the guidelines require it.
  • Do not assume the rules are stable; recheck before each update.

08How to measure it

  • Track plugin usage and sign-ups from ChatGPT.
  • Track support questions about the plugin.
  • A realistic test: two to three months after listing.

09Time budget

  • Before: 20 to 60 hours.
  • Ongoing: 2 to 4 hours a month.

10Pair it with

11Sources

Sources