Two ways customers use your product
- Approved by
- Panaversity ·
Both ways serve individuals and teams alike. What differs is how people work.
Through conversation. A connector links the AI assistant to your server. The customer adds it, signs in, and then simply asks the AI for help. The AI calls your server, and your server decides what that customer has paid for.
A connector can be added on its own. You can also package it in a plugin, which bundles skills, connectors and subagents into one package, so the customer sets everything up at once.1 There are no screens to build, but the customer has to know what to ask.
Through a guided app. Many people will never write a good request to an AI. They need a screen with buttons, tables and a guided workflow. There are two ways to give them one:
- An MCP App. Your server shows its own screens inside the chat, through MCP Apps, an official, optional extension to MCP.2 A customer asks for their open invoices and gets a table with an Approve button beside each one, not a list of text. The same screen works in every AI app that supports MCP Apps, including Claude, ChatGPT and Microsoft 365 Copilot.2,3 Claude calls these interactive connectors.4
- An Artifact. On Claude only, the app can also be an Artifact that calls Claude.5
An MCP App is part of your connector, so it reaches every customer who adds the connector. An Artifact calls the AI to do the work each time someone uses it. On Claude, an Artifact can use connectors on the Pro, Max, Ultra, Team and Enterprise plans, and each person connects their own apps, even in a shared Artifact.6
An MCP App adds a screen to a tool. It does not replace the tool's answer. Each tool should still return useful text, so a customer whose AI app cannot show screens still gets a result.2
Both ways use the same server. Build the first, and the second is an addition, not a rewrite. But reusing the server does not solve distribution. You still have to get the product to each customer, set it up and keep it updated.
Setup is an important obstacle to adoption. Before anything works, each customer usually has to add your connector and sign in. In a company, an owner must first turn on connectors for the organization. Each person then signs in separately, unless the connector uses one shared credential.7
On Claude Team and Enterprise, an administrator can authorize a connector once for everyone through enterprise-managed authentication. It works only if your connector supports it.8
For someone who has never done this, setup is a real hurdle, and it falls on the non-technical users a guided app is meant to reach. Write a short setup guide. Then test, in a real customer workspace, how a customer receives the product, turns it on and gets updates.
Sources
- Use plugins in Claude, Claude Help Center.↑
- MCP Apps, Model Context Protocol, accessed 15 November 2026.↑↑2↑3
- MCP Apps compatibility in ChatGPT, OpenAI Developers, accessed 15 November 2026.↑
- Your favorite work tools are now interactive connectors inside Claude, Anthropic, 26 January 2026.↑
- What are artifacts and how do I use them?, Claude Help Center.↑
- What are artifacts and how do I use them?, Claude Help Center, accessed 31 October 2026.↑
- Use connectors to extend Claude's capabilities, Claude Help Center.↑
- Authorize MCP connectors for your entire organization, Claude Help Center.↑
- Owner
- Panaversity