--- title: "MCP Apps: When Your Business Runs Inside ChatGPT or Claude" description: "Getting cited by AI makes you visible. Being connected makes you usable. What the MCP Apps standard, ratified in January 2026, changes for your business." url: https://www.weftd.com/resources/insights/mcp-apps-business-inside-chatgpt-claude locale: en alternates: en: https://www.weftd.com/resources/insights/mcp-apps-business-inside-chatgpt-claude fr: https://www.weftd.com/fr/resources/insights/mcp-apps-votre-activite-dans-chatgpt-claude --- # MCP Apps: When Your Business Runs Inside ChatGPT or Claude Getting cited by AI makes you visible. Being connected makes you usable. What the MCP Apps standard, ratified in January 2026, changes for your business. _Charles Cousyn · 2026-07-23 · MCP App, AI presence, GEO, agentic web, acquisition_ Everyone is optimizing to get quoted by AI right now. GEO, AEO, AI-ready content: the same instinct as SEO, aimed at assistants instead of search engines. It works, and it is worth doing. It is also the smaller half of the story. ## TL;DR - A citation puts your name inside an answer. The user still has to click, compare, decide, and act somewhere else. - A connected app, or MCP App, runs inside the assistant: the customer uses it without leaving the conversation. - Both the trigger and the economics change: you stop depending on being found, and you stop paying per visit. ![Being cited is not being used. On the left, GEO or AEO: your name appears, the user still has to go elsewhere. On the right, an MCP App: your service runs and the action completes in the conversation.](/images/cited-vs-connected.svg) ## What a citation actually gives you A citation puts your name inside an answer. That is visibility, and it is not nothing. But it stops there: the user still has to click, compare, decide, and act somewhere else. Every step loses part of them along the way, and you will never know how many. That is already the subject of [why getting cited isn't enough](/resources/insights/getting-cited-by-ai-isnt-enough). What follows is a different matter. ## What an MCP App is An MCP App is an application that runs inside the assistant. The standard that makes it possible was ratified in January 2026 as an official extension to the Model Context Protocol. It lets a service deliver a real interface, which the assistant renders inside the conversation and the user handles directly. Concretely, instead of a paragraph that talks about you, the customer sees your module: your availability, a button to book, a form to order. The assistant becomes an interface, not just a responder. It is no longer a page to quote. It is a capability to use. This is not a distant prospect. Since January 2026, nine applications already run inside Claude, including Slack, Figma, Asana and Canva. On the ChatGPT side, whose app ecosystem rests on the same protocol, you find names far more telling for a local business: Booking.com, Expedia, Zillow. In other words, the intermediaries that take a commission on your business are already in there. You are not. Two details are worth knowing. These interfaces run in a sandboxed frame, and every action triggered goes through the same checks as a regular tool call, so nothing runs without the user's knowledge. And the protocol belongs to no single vendor, having been handed to an independent foundation at the end of 2025. You are not locking yourself into anyone's ecosystem. ## The trigger changes This is the part most people miss. A citation depends on a chain of events you do not control: the assistant has to find your page, judge it relevant, and choose to mention you. A lot of conditions, none of them yours. A connected capability works the other way around. It answers a described need. When someone says "I want to book a table for two tonight," the assistant looks for a capability that does exactly that. Whether or not the customer knows your name stops mattering. > A citation depends on how well known you are. A connected capability depends on how useful you are. For a local business with little online visibility, the difference is enormous. You stop fighting to be known and start being picked because you can do the thing that was asked. ## The economics change too Paid discovery charges per visit, every visit, in an auction where you bid against better-funded competitors. The day you stop paying, the flow stops. A connection happens once. After that, every matching request arrives without an auction and without a cost per visit. You are no longer renting visibility, you are installing a capability that stays. That is not an accounting detail, it is a difference in kind. The first model is a recurring expense, the second is an asset you build. ## What this changes for your business A restaurant no longer just appears in a list: the customer sees a free table at 8 pm and books it inside the conversation. A tradesperson exposes their slots, and the appointment is set without a single phone call. A hotel shows real availability at the moment the traveler is planning. An online store lets people add to cart right where the question was asked. In every case, the same shift: the conversation stops being a dead end that sends people elsewhere, and becomes the place where the deal closes. ## What this does not solve The limits deserve to be said plainly. You still have to be connected. A capability nobody has plugged in is useless, and the discovery mechanisms are being built right now. Adoption varies. Not every assistant handles these interfaces the same way yet, and the standard is moving fast. And nobody controls AI answers. Being usable strongly improves your odds of being picked, it does not guarantee them. Be wary of anyone who promises otherwise. ## Being cited is visibility. Being connected is business. GEO is still useful, and it should be done. But it gets you mentioned, while the other gets you used. One depends on an algorithm choosing you, the other on a need you know how to meet. **[Create your AI presence →](/#early-access)** ## FAQ **Isn't an MCP App just another chatbot?** No. A chatbot answers on your site, to people already there. An MCP App runs inside the assistant your customers already use, and enables a real action, not just an answer. **Do I need to be a developer to publish one?** No, not if you go through a no-code [AI presence](/resources/academy/what-is-an-ai-presence). The standard is technical, the usage should not be: you describe your business and the possible actions, the rest is automated. **Which assistants does it work with?** The standard is open and readable by compatible assistants, notably those from OpenAI and Anthropic. Capabilities still vary from one assistant to the next, and adoption is moving quickly. **Do I stay in control of what runs?** Yes. You decide which actions are exposed, and every action triggered from the interface goes through the same checks as a regular call, with the user's consent. **Should I drop GEO and SEO?** No. They remain useful for visibility. A connected capability adds what they do not: the action, at the moment the customer decides. ## Sources - Model Context Protocol, MCP Apps specification of January 26, 2026 ([link](https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx)) - Anthropic, interactive apps in Claude, January 2026 ([link](https://claude.com/blog/interactive-tools-in-claude)) - Model Context Protocol, official documentation ([link](https://modelcontextprotocol.io)) - Model Context Protocol Blog, 2026-07-28 release candidate ([link](https://blog.modelcontextprotocol.io/posts/2026-07-28-release-candidate/))