ChatGPT Plugin Directory
The ChatGPT plugin directory is OpenAI's official listing of installable plugins, shared by ChatGPT and Codex. It replaced the app directory in July 2026. It shows you what exists and lets you install it; it does not rank quality or tell you which plugin is better for a given task.
What it is
The plugin directory is the official, first-party place to find and install plugins. ChatGPT and Codex share one universal directory, so a public plugin resolves to the same listing from supported surfaces in either product. Inside it, plugins are organised into tabs — ones built by OpenAI, ones provided by your workspace, and a Personal tab covering plugins you created or that were shared with you — plus a separate row for what you have already installed. That scoping is part of why published counts disagree: they are not all counting the same set. It succeeded the App directory in July 2026, and existing app connections were not broken by the change — you add new plugins from the directory, authenticating the underlying service as before.
What it lists
Everything approved through OpenAI's plugin submission review: skills-only plugins that package reusable workflows, MCP-only plugins that connect to an external service, and plugins that combine both. That mix is worth knowing before you browse, because two adjacent listings can be completely different kinds of product — one is a set of instructions, the other is a live connection to your account.
How OpenAI ranks placement
OpenAI's plugin guidelines describe the published standard as the minimum bar a plugin must meet to remain available in the directory, and say plugins that demonstrate strong real-world utility and high user satisfaction may become eligible for enhanced distribution — directory placement or proactive suggestions in conversation. So placement reflects OpenAI's own utility and satisfaction signals plus policy compliance. It is not an independent quality score, and it is not comparative: the directory will not tell you that one of two similar plugins is meaningfully better at the job.
Why discovery is still the weak point
This is the ecosystem's most-reported problem, and it is a reasonable thing to be frustrated by. Published figures for the directory's size range from about 300 to over 1,600 depending on whether you count only service-backed integrations or every listing, and partner companies have publicly said users struggle to find them and that the surface has driven little traffic. A first-party directory is optimized for install flow and policy compliance, not for the question people actually arrive with, which is comparative: which of these is best for my task, does it work on my plan, in my country, and is it still maintained.
How this site complements it
Use the official directory to install. Use an independent ranking to decide what to install. We score each MCP-backed plugin 0–100 across seven criteria, publish a last-tested date and the evidence behind every status, and flag apps that are region-limited, business-only, or no longer working rather than leaving them to look available.