TAU-HOME.COM
LOADING

Build a ChatGPT Plugin with Codex: openai/mcp-extensions Repo Mention

Max Stoiber (@mxstbr) pointed Codex at the openai-named mcp-extensions repository as the starting point for ChatGPT plugin development. Repository location, pos

tau · October 9, 2026

#ChatGPTPlugin #MCP #Codex #OpenAI #DevTools

Build a ChatGPT Plugin with Codex: openai/mcp-extensions Repo Mention

Verified account Max Stoiber (@mxstbr) posted on October 9, 2026 at 00:44 KST, telling developers to point Codex at https://github.com/openai/mcp-extensions to start building a ChatGPT plugin. The post body is a single sentence, and the link destination resolves to https://github.com/openai/mcp-extensions.

Screenshot-style illustration of a developer pointing a coding agent at the openai mcp-extensions GitHub repository to start a ChatGPT plugin project

Image source: @mxstbr via X

The original post contains one sentence, a repository link, and one image. Only the author, timestamp, and link destination are verified; engagement figures (views, likes, bookmarks) are not in this evidence bundle and are not covered here.

What This Repo Is and Who It Helps

openai/mcp-extensions is the openai-named GitHub repository presented as the starting point for building ChatGPT plugins. Whether it is an official repository, plus its README contents and support scope, were not included in this verification bundle and are unverified. The proposed workflow is to hand the repository URL directly to a coding agent like Codex and begin plugin development.

  • Who it helps: developers who want to build ChatGPT plugins or integrations, and developers experimenting with MCP-based work through Codex
  • Verified usage path: the only verified instruction is the one sentence from the original post — point Codex at https://github.com/openai/mcp-extensions and start building a ChatGPT plugin
  • Unverified scope: the repository's README contents, install and run steps, supported clients and versions, and license terms were not included in this verification bundle and are not covered here. Check the original repository directly before doing real work

Deployment and Operations Mentions Confirmed in the Thread

Replies in the same thread contain individual developers' questions and the author's answers about plugin deployment. These are individual case statements in the thread, not official documentation.

  • Flat MCP structure and endpoint question: one replier, describing a flat MCP structure requirement with no discovery tooling, asked whether deploying a new plugin is faster than waiting for an endpoint change to /mcp/openai. The author (@mxstbr) answered: "deploy a new one will be faster!"
  • Testing difficulty inside Codex: another replier said verifying work is hard because computer use is unavailable in the Codex app. The author agreed it is difficult right now, said developer-experience improvements are planned, and shared one link to try in the meantime for those comfortable with the risk.
  • Review and approval waits: several replies mention a long review process or waiting days for approval. Review timelines and developer-verification issues are individual statements and are not confirmed as official review criteria.

Why It Is Worth Noticing Now, and Its Limits

What matters is that an openai-named repository was directly named as the starting point for ChatGPT plugin development. Passing a single URL to Codex keeps the entry barrier low.

The limits are equally clear. This verification relies only on X thread evidence; the repository's internal docs and setup steps were not verified. Thread mentions of flat-structure requirements, endpoint paths, and review timelines cannot be generalized. Anyone proceeding to build a plugin should compare the openai/mcp-extensions repository itself against the official ChatGPT plugin guidance.

Sources