--- title: "MCP Apps: your software inside AI assistants | Vuelance" description: "AI assistants can now show working pieces of other software inside the chat, through one open standard. What that means for products and internal tools." canonical_url: "https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools" last_updated: 2026-02-04 meta: "og:description": "AI assistants can now show working pieces of other software inside the chat, through one open standard. What that means for products and internal tools." "og:image": "https://vuelance.com/_og/s/o_dd7d2dcff02a7164.png" "og:image:alt": "MCP Apps: your software inside AI assistants" "og:image:height": "630" "og:image:type": image/png "og:image:width": "1200" "og:title": "MCP Apps: your software inside AI assistants | Vuelance" "twitter:image": "https://vuelance.com/_og/s/o_dd7d2dcff02a7164.png" "twitter:image:alt": "MCP Apps: your software inside AI assistants" --- > Index of every page on this site: [llms.txt](https://vuelance.com/llms.txt) # **MCP Apps: your software inside AI assistants** AI assistants can now show working pieces of other software inside the chat, through one open standard. What that means for products and internal tools. Reviewed by **Ali Hassan** · Founder 4 min read · 4 Feb 2026 [Share on X](https://x.com/intent/post?text=MCP%20Apps%3A%20your%20software%20inside%20AI%20assistants&url=https%3A%2F%2Fvuelance.com%2Fblog%2Fmcp-apps-your-software-inside-ai-tools) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fvuelance.com%2Fblog%2Fmcp-apps-your-software-inside-ai-tools) [Share on WhatsApp](https://wa.me/?text=MCP%20Apps%3A%20your%20software%20inside%20AI%20assistants%20https%3A%2F%2Fvuelance.com%2Fblog%2Fmcp-apps-your-software-inside-ai-tools) Last week the Model Context Protocol, the open standard that lets AI assistants use outside software, got its [**first official extension**](https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/). It is called MCP Apps, and it lets a tool send back a small interactive interface instead of just text. That interface appears inside the conversation: a form, a chart, a map, a preview with buttons. It went live straight away. [**Claude now shows interactive versions**](https://claude.com/blog/interactive-tools-in-claude) of Slack, Asana, Figma, Canva, Box, monday.com and a handful of others, in its web and desktop apps. You can ask Claude to draft a Slack message and see it formatted, edit it, then send it. You can turn a messy list into an Asana project timeline without opening Asana. Block's goose agent supports it too, as do preview builds of Microsoft's VS Code, and OpenAI, which helped write the standard, said ChatGPT support would start rolling out the same week. In November [**we wrote about generative UI**](https://vuelance.com/blog/generative-ui-explained), the idea that AI should answer with interfaces as well as words. This is the practical, standardised version of that idea, and it arrived faster than we expected. ## **Why one standard matters** Until now, putting your product inside an AI assistant meant picking a platform. OpenAI's apps in ChatGPT, launched in October, used their own SDK. Other assistants had their own approaches, or none. MCP Apps was written jointly by people from Anthropic, OpenAI and the open-source MCP-UI project, so the same app can appear in several assistants. You build the interactive piece once, as a small web page bundled with your MCP server, and each assistant that supports the standard displays it. The security model is sensible. The interface runs in a sandboxed frame, separated from the conversation and the rest of the assistant. The assistant can check it before showing it, and can require the user to approve any action the interface tries to take. Messages between your app and the assistant go through a channel that can be logged. ## **What it is good for in a customer product** The best uses are moments where a customer is already asking an AI for help and a little interface beats a paragraph. - A property search that returns a map and a shortlist, not ten addresses in a list. - A quote calculator where the customer adjusts quantities and sees the price change. - A booking widget showing real slots, which books on a tap after the customer confirms. - An order or shipment tracker with the next step as a button. All of these could live on your website too. The difference is that the customer does not have to leave the assistant, find you and start again. Whether that is worth building depends on how many of your customers ask AI tools for help in your category, which is worth checking before you spend money. ## **The quieter opportunity: internal tools** The bigger change for many businesses may be internal. Teams already spend part of their day in Claude or ChatGPT. Most of the data they need lives elsewhere: the CRM, the stock system, the sales spreadsheet, a custom dashboard someone built three years ago. Until now, AI tools could fetch that data as text, which was useful but awkward. With MCP Apps, your internal systems can show up properly inside the assistant. A manager asks "how did the Sharjah branch do this week?" and sees the branch dashboard with its usual charts. A salesperson asks to prepare a quote and gets your quote form, filled in from the conversation, ready to check and send. Staff stay in the assistant they already use. For a business with a few custom internal systems, this is often a better first project than a public app. The users are your own staff, access runs through your organisation's AI accounts, and the time saved is easy to measure. ## **What to watch out for** The standard is days old in production. Some things are still settling: - Each assistant decides how and when to show your app, and those rules differ. - Discovery is uneven. ChatGPT has an app directory, Claude has its connectors directory, and how users find apps beyond that is unclear. - Anything that changes data, such as sending, booking or paying, should always need a clear confirmation from the user. Design for that from the start. - Treat third-party MCP servers like any software you install. Connect only ones you trust, with the narrowest access they need. ## **Where we would start** Pick one task that your team or your customers do often, where they currently switch between an AI assistant and another screen. Build the MCP server for it first, with the actions it needs and the data rules around them. Then add a single interactive view for the moment where text falls short. If the assistants change their rules, you keep the server and your data model. If they keep moving in this direction, as they have every month since October, you are already in place. **// Keep reading** ## Recommended for you [**All articles**](https://vuelance.com/blog) - ### [Generative UI, one year later](https://vuelance.com/blog/generative-ui-a-year-later) ChatGPT now answers with interactive charts and calculators, and other companies' apps live inside AI assistants. What the year settled, and what it did not. [**Continue reading**: Generative UI, one year later](https://vuelance.com/blog/generative-ui-a-year-later)3 min read - ### [What an AI assistant on your website should actually do (and what it should never do)](https://vuelance.com/blog/what-an-ai-assistant-should-do) Most business chatbots answer questions badly. Here is the small set of jobs an assistant can do well today: answering from your own content, guiding a visitor to the right page, and handing over to a human at the right moment. [**Continue reading**: What an AI assistant on your website should actually do (and what it should never do)](https://vuelance.com/blog/what-an-ai-assistant-should-do)4 min read - ### [Five jobs to automate before you hire again](https://vuelance.com/blog/five-jobs-to-automate) The repetitive work that eats a small team’s week, and which parts software can take over safely. [**Continue reading**: Five jobs to automate before you hire again](https://vuelance.com/blog/five-jobs-to-automate)3 min read ```json {"@context":"https://schema.org","@graph":[{"@id":"https://vuelance.com/#website","@type":"WebSite","description":"Vuelance is an AI-native company with forward deployed engineers. Websites, apps, software and AI automation for startups and growing businesses, with a first working demo in about 2 weeks.","name":"Vuelance","url":"https://vuelance.com/","publisher":{"@id":"https://vuelance.com/#identity"}},{"@id":"https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools#webpage","@type":"WebPage","dateModified":"2026-02-04","datePublished":"2026-02-04","description":"AI assistants can now show working pieces of other software inside the chat, through one open standard. What that means for products and internal tools.","name":"MCP Apps: your software inside AI assistants","url":"https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools","isPartOf":{"@id":"https://vuelance.com/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools"]}],"primaryImageOfPage":{"@type":"ImageObject","url":"https://vuelance.com/img/abstract/mesh-glow.webp","inLanguage":"en","contentUrl":"https://vuelance.com/img/abstract/mesh-glow.webp"}},{"@id":"https://vuelance.com/#identity","@type":"Organization","description":"Vuelance is an AI-native company with forward deployed engineers. Websites, apps, software and AI automation for startups and growing businesses, with a first working demo in about 2 weeks.","duns":"772053576","email":"contact@vuelance.com","foundingDate":"2025","legalName":"Vuelance LLP","name":"Vuelance","telephone":"+91 79071 41635","url":"https://vuelance.com","address":{"@type":"PostalAddress","streetAddress":"Second floor, KP Tower, Thurakkal","addressLocality":"Manjeri","addressRegion":"Keralam","postalCode":"676122","addressCountry":"IN"},"contactPoint":{"@type":"ContactPoint","contactType":"sales","email":"contact@vuelance.com","telephone":"+91 79071 41635"},"logo":{"@id":"https://vuelance.com/#logo"},"sameAs":["https://facebook.com/vuelance/","https://instagram.com/vuelance_","https://x.com/vuelance_","https://linkedin.com/company/vuelance/","https://youtube.com/@vuelance"]},{"@id":"https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools#article","articleSection":"AI","dateModified":"2026-02-04","datePublished":"2026-02-04","description":"AI assistants can now show working pieces of other software inside the chat, through one open standard. What that means for products and internal tools.","headline":"MCP Apps: your software inside AI assistants","inLanguage":"en","thumbnailUrl":"https://vuelance.com/img/abstract/mesh-glow.webp","@type":["Article","BlogPosting"],"author":{"@id":"https://vuelance.com/#/schema/person/1"},"image":{"@id":"https://vuelance.com/#/schema/image/1"},"isPartOf":{"@id":"https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools#webpage"},"mainEntityOfPage":{"@id":"https://vuelance.com/blog/mcp-apps-your-software-inside-ai-tools#webpage"},"publisher":{"@id":"https://vuelance.com/#identity"}},{"@id":"https://vuelance.com/#/schema/person/1","@type":"Person","jobTitle":"Founder","name":"Ali Hassan","url":"https://vuelance.com/about","image":{"@id":"https://vuelance.com/#/schema/image/2"}},{"@id":"https://vuelance.com/#logo","@type":"ImageObject","caption":"Vuelance","contentUrl":"https://vuelance.com/img/logos/vuelance-mark-512.png","inLanguage":"en","url":"https://vuelance.com/img/logos/vuelance-mark-512.png"},{"@id":"https://vuelance.com/#/schema/image/1","@type":"ImageObject","contentUrl":"https://vuelance.com/img/abstract/mesh-glow.webp","inLanguage":"en","url":"https://vuelance.com/img/abstract/mesh-glow.webp"},{"@id":"https://vuelance.com/#/schema/image/2","@type":"ImageObject","contentUrl":"https://vuelance.com/img/team/ali-hassan-avatar.webp","inLanguage":"en","url":"https://vuelance.com/img/team/ali-hassan-avatar.webp"}]} ``` ## Sitemap See the full [sitemap](https://vuelance.com/sitemap.md) for all pages.