ChatGPT & MCP Apps are quickly becoming a powerful new distribution channel for products, tools, and startups. Because **[Fractal](/content/site-root.html)** is the #1 choice for building and deploying ChatGPT & MCP Apps, we get asked this question a lot: **_How do ChatGPT & MCP Apps actually get discovered?_** If you are building ChatGPT & MCP Apps, or thinking about using them for growth, this guide explains how discovery works today, what OpenAI is optimizing for, and how to position your app to be surfaced inside ChatGPT. * * * ## Why ChatGPT & MCP Apps Matter for Growth and Distribution OpenAI recently opened the **ChatGPT App Store** to developers. This unlocks access to **over 800 million weekly users** directly inside ChatGPT. That scale is exactly why ChatGPT & MCP Apps are such a powerful opportunity for growth and distribution. Instead of relying only on SEO, ads, or app stores, ChatGPT & MCP Apps allow your product to appear directly inside user conversations, exactly when intent is highest. That opportunity is massive, but only if your app actually gets discovered. Discovery inside ChatGPT does not work like a traditional marketplace. There are no categories to browse, no rankings to game, and no paid placements. Instead, discovery is context-driven. * * * ## How ChatGPT & MCP Apps Get Discovered Now When a user types a prompt, ChatGPT evaluates whether a third-party app could provide a better result than a text-only answer. If ChatGPT believes an app improves the experience, it may **suggest or surface that app directly in the conversation**. For example: - Asking about houses may surface a real estate app - Asking about recipes may surface a grocery shopping app This suggestion moment is what discovery looks like inside ChatGPT. Once the user installs the app, it can then be used in two ways: 1. When the user explicitly asks ChatGPT to use the app 2. When ChatGPT automatically decides to invoke the app to improve the response Another layer of discovery happens when ChatGPT invokes the app. * * * ## OpenAI's Vision for ChatGPT & MCP Apps OpenAI has been clear that ChatGPT is moving beyond a purely text-based interface. In [The Shift from Text to More Dynamic AI Experiences](https://fidjisimo.substack.com/p/more-dynamic-ai-experiences), **Fidji Simo, President of OpenAI**, explains that humans do not think only in words. Many ideas start as visuals, interactions, or actions. Because of this, ChatGPT is evolving toward a fully generative UI that dynamically brings in the right components based on what the user wants to do. This vision directly explains how ChatGPT & MCP Apps get discovered. Apps are surfaced when they offer something text alone cannot. * * * ## The Core Rule of ChatGPT & MCP App Discovery There is one simple rule: **Your app gets discovered when it provides a better experience than ChatGPT's text-only answer.** Not longer responses. Not spamming keywords in your app description. A genuinely better outcome for the user. OpenAI has outlined three categories of ChatGPT & MCP Apps that consistently outperform text-only responses. * * * ## The 3 Types of ChatGPT & MCP Apps That Get Discovered ### 1\. Know: Apps with Data ChatGPT Does Not Have ChatGPT does not have access to live data, private user data, or proprietary systems. Apps do. A classic example is the **Zillow app**. Zillow knows the real-time inventory of homes on the market. ChatGPT does not. If your app has access to live, proprietary, or user-specific data, it immediately becomes valuable and discoverable. Many builders use **[Fractal](/content/site-root.html)** to connect external data sources and surface that data directly inside ChatGPT & MCP Apps. * * * ### 2\. Do: Apps That Take Action ChatGPT can explain how to do things, but it cannot take real-world actions. Apps can. A strong example is the **Instacart app**. Instacart actually shops for you, turning grocery lists into groceries at your front door. If your app can take actions like ordering, booking, sending, or executing workflows, ChatGPT has a clear reason to surface it. This is one of the most effective ways to leverage ChatGPT & MCP Apps for distribution. * * * ### 3\. Show: Apps That Are Better Than Text ChatGPT is still fundamentally text-based. If your experience is visual, interactive, or playable, an app will outperform text every time. A good example is a **Trivia app** I built with **[Fractal](/content/site-root.html)**. ChatGPT can generate trivia questions as text, but turning those questions into an interactive, playable experience is far more engaging. Being able to see the question, interact with it, and play the game creates an experience text alone cannot match. **[Fractal](/content/site-root.html)** makes it ultra easy to build these kinds of interactive ChatGPT & MCP Apps. All you need is an idea. * * * ## The Real Benchmark for Discovery ChatGPT's goal is simple: Deliver the best possible experience to the user. A good benchmark for builders is: **For the prompts your app targets, can your app provide a better answer or experience than ChatGPT could on its own?** If the answer is yes because your app knows more, does more, or shows more, ChatGPT has a strong incentive to surface it. * * * ## Learn How to Build ChatGPT & MCP Apps If you want a practical walkthrough of: - How ChatGPT & MCP Apps get discovered - How to leverage ChatGPT & MCP Apps for growth - How to leverage ChatGPT & MCP Apps for distribution - ChatGPT & MCP Apps tips and tricks - How to build with the OpenAI Apps SDK I have a YouTube playlist that covers how to build ChatGPT & MCP Apps with **[Fractal](/content/site-root.html)** here: [Watch the YouTube Playlist](https://www.youtube.com/watch?v=ipws4NK92-0&list=PLIWpfZmcbJqhc44SwCcHKQrsCNXTkHp7i) Whether you are experimenting with the OpenAI Apps SDK or building production apps with **[Fractal](/content/site-root.html)**, ChatGPT & MCP Apps represent a powerful new distribution surface. ## Ready to Build Your ChatGPT & MCP Apps? Start building with Fractal today and get your app discovered by millions of ChatGPT users. **[Get Started](/content/site-root.html)**