NewsAnalysis

Claude Picks the App. What That Means for AI Distribution.

WaniWani
·

Last updated: May 2026

On April 23, 2026, Anthropic shipped fifteen consumer connectors to Claude: Booking.com, Uber, Instacart, Intuit TurboTax, Spotify, AllTrails, Tripadvisor, Resy, StubHub, Audible, Taskrabbit, Thumbtack, Viator, Credit Karma, Uber Eats. Most of the press covered it as feature news.

It is not just feature news. It is confirmation of a distribution shift that started with OpenAI’s ChatGPT App Store, and the category most affected is services. Hotel bookings. Rides. Tax filings. Restaurant reservations. Trip planning. Credit and insurance quotes likely follow. These are not productivity tools that engineers plug into their workflow anymore; they are services that consumers transact with, and the way a buyer reaches them inside Claude works nothing like search, social, or even ChatGPT’s app store. For any business that sells a service (and increasingly that is every business), the rules of distribution just changed.

At WaniWani we build AI distribution infrastructure for service businesses across both surfaces. What we have watched over nine months of MCP deployments is the shape of this new channel coming into focus.

The shift sits in one sentence Anthropic published the same day:

“Claude now suggests the right app for what you’re doing, like finding a reservation, adding to a grocery cart, or identifying a flight. It’s working from what you’ve told it: your preferences, your context, your conversation.” (Anthropic blog, April 23, 2026)

Read fast, that is product copy. Read slowly, it is a different distribution model than ChatGPT’s. The user is not browsing a store. The user is having a conversation, and the model is deciding which third-party service belongs in the answer.

Here are the three things this changes for service businesses.

1. ChatGPT built a store. Claude built a recommendation engine.

On ChatGPT, the user picks the app. They install it, route their question to it, and click Allow on each tool call. The mental model is plugin selection.

On Claude, the user does not pick. Anthropic’s docs are explicit: “Directory connectors are eligible for Suggested Connectors, in-chat recommendations when relevant to the user’s task. Every directory entry is included automatically.” (claude.com/docs/connectors/directory) PYMNTS, covering the launch, named the architectural distinction: “Gemini connects primarily to Google’s own app ecosystem. ChatGPT relies on users selecting tools manually. In contrast, Claude now suggests the right app based on what the user is doing inside the conversation.”

The unit of competition changes. On a store, you compete for the click; the user reads two app cards and chooses one. On a recommendation engine, you compete for inclusion in the candidate set and then for the model’s rank-1 pick. The user never sees the apps Claude did not surface, because Claude does not surface them.

The competitive set per conversation collapses to zero, one, or a handful, and most users only act on the rank-1 option. There is no second-page traffic to scrape, no long tail to compete on. You either win the slot or you do not exist in that conversation.

This is the state today, not a permanent law. ChatGPT’s Apps SDK launched in October 2025 on MCP, and model-suggested behaviors are creeping into its surface. Our own research (WaniWani Research Vol. 1) showed that what AI assistants say about a brand can be moved with published content and structured signal. The suggestion mechanic is not unmovable; it is just unbought. The reverse can happen too: Anthropic could add commerce primitives or change its ad policy. What is durable is the underlying principle. When the model picks, metadata is the lever. When the user picks, marketing is. Service businesses selling through AI need to be set up to compete on both surfaces, because both surfaces will keep evolving in both directions.

Why this matters more for services than for products. A commodity product has a clean fit with the classic search-and-click stack: the user knows what they want, types a brand or category, and picks from a list. Services do not work that way. Insurance, banking, mortgages, travel planning, tax filing are personalized, conversation-led, and high-intent. The buyer is not browsing a list; they are describing a situation and expecting an answer specific to it. That is the conversation Claude’s connector surface is designed for, and it is a better fit for how services actually sell than any channel that came before it.

2. Claude’s connector mechanic came from coding, not consumer AI.

Claude was the coding-and-careful-reasoning AI for most of 2024 and 2025. By early 2026 that had shifted. In February, Claude hit #1 on Apple’s US App Store, overtaking ChatGPT. Anthropic reported daily sign-ups had quadrupled and free active users were up over 60% since the start of the year. Claude Mobile, Claude Design, the Super Bowl ad about not running ads, all of it positioned Claude as a mass-consumer brand. The April 23 connector release fits the same pivot: Claude is no longer a developer-and-enterprise tool with consumer features attached. It is a general-purpose assistant where the developer-grade architecture is the foundation, not the ceiling.

What most coverage missed is that the connector mechanic underneath did not change with the audience. It is the mechanic Anthropic shipped for developers on November 25, 2024, when MCP launched. The April 2026 release is the third act of a three-stage rollout:

  • November 25, 2024. MCP launches. Audience: developers. Anthropic’s framing in its own words: “a new standard for connecting AI assistants to the systems where data lives, including content repositories, business tools, and development environments.” The named adopters were Block and Apollo, and the development tools companies were Zed, Replit, Codeium, and Sourcegraph. No consumer applications.
  • July 2025. Connector directory launches. Audience: work. The early directory was productivity-heavy: Gmail, Slack, Notion, Asana, Canva, Google Drive. Still operator-grade software, not consumer services.
  • April 23, 2026. Personal connectors launch. Audience: consumers transacting. Booking, Uber, Instacart, TurboTax. The same protocol that ran the developer surface for seventeen months and the work surface for nine now runs commercial services.

For seventeen months between MCP’s launch and the consumer connector release, Claude Code ran this mechanic at scale on the most demanding category there is: agentic coding. By 2026, Claude Code was the most popular agentic coding tool among professional developers and enterprises (Zapier, 2026). In that workflow, the model routinely composes four, five, or ten tool calls per turn: read a file, search a repo, run a test, write a patch, open a PR. Tool selection across competing MCP servers, composability across multiple servers in a single turn, metadata-driven discovery, all of it was load-tested before any consumer ever saw a Connect button.

What changed in April 2026 was the audience, not the architecture. Booking.com is a connector in the same shape postgres-mcp-server is a connector. AllTrails is metadata-discoverable the way an internal company MCP server is metadata-discoverable. The user no longer types the JSON config themselves; they click Connect. But what happens after the click is the same selection loop Claude has been running for developers since late 2024.

That heritage explains three behaviors that look surprising from a pure-consumer-AI lens:

  • Composability. Claude chains multiple connectors confidently in a single turn. Builders shipping on both platforms have flagged this gap: “ChatGPT apps generally only select a single tool at a time. That sounds fine until you realize that most useful financial questions require composing multiple tools together.” (r/ClaudeAI builder thread) Composability was a coding requirement before it was a consumer feature.
  • Metadata as the lever, not paid placement. The developer ecosystem never had ads. The only way a github-mcp-server ever earned a tool call was a clear name and a clear description. Anthropic’s Skills documentation, which uses the parallel mechanism, states this directly: “The ‘name’ and ‘description’ in a Skill’s metadata are particularly critical, as Claude uses these when deciding whether to trigger the Skill.” The norm transferred to the consumer directory unchanged.
  • Ad-free as a commitment. The audience that built up the connector culture (developers writing open-source MCP servers) would have rejected paid placement on principle. The consumer surface inherits that culture before it inherits any monetization model that might compromise it.

OpenAI’s apps mechanic carries the opposite lineage. ChatGPT Plugins (March 2023) became the GPT Store (November 2023), then Instant Checkout (September 2025), then the Apps SDK (October 2025, built on MCP). By March 2026, OpenAI was scaling back native checkout: only about twelve of a million eligible Shopify merchants had integrated, and transactions were shifting back into merchant-owned apps. The plumbing converged at the protocol level; the consumer surface still carries the plugin-store DNA: a user-installed app the assistant invokes on demand.

Anthropic built agents that reach for tools. OpenAI built apps that a user opens. That divergence is the cleanest single explanation for why the two consumer surfaces feel different in 2026, despite running on the same protocol underneath.

For service businesses, two practical consequences fall out of this. First, the same MCP server cannot be optimized identically for both surfaces today. On ChatGPT, you are building an app (a destination the user installs, designs around widgets, with eventual paid placement and native checkout). On Claude, you are building a tool (a metadata-described capability the model reaches for, scored on description quality and composability). Same code. Different product, for now. Both surfaces are evolving fast, and the durable position is to build a server that reads cleanly under whatever the model surface looks like in twelve months, not just today.

Second, the maturity argument changes the time-to-market math. Services tempted to wait for the platforms to settle should know the protocol has been load-tested for eighteen months on the most demanding category there is. The infrastructure to be a distribution endpoint on Claude exists today. The platforms accepting service categories (insurance, banking, broadband, mortgages) are actively pulling vendors in. The shape is stable enough to build against, and the longer a service waits, the more usage signal competitors accumulate on the ranking flywheel.

3. Three levers, no paid lane: inclusion, metadata, usage.

The recommendation engine Anthropic just shipped has no SEM equivalent. The blog is explicit: “Claude is ad-free and will stay that way. There are no paid placements or sponsored answers in conversations with Claude.” (April 23, 2026) The Anthropic docs go one further and disclose the actual ranking signal: “Ranking is usage-based, similar to other app stores.” (claude.com/docs/connectors/directory)

That leaves three documented levers for any service business that wants to win on this surface:

  1. Directory inclusion (the gate). Anthropic vets every entry for security, reliability, and compatibility before it appears in the directory. Custom (self-installed) connectors exist and work fine for power users, but they are not in the directory and they cannot be model-suggested to anyone else. For consumer-scale distribution, directory submission is the prerequisite. Treat it as the equivalent of getting your store live in 2010, not as a developer experiment.
  2. Metadata (the cold-start lever). Before any usage signal exists, the model picks based on what your connector’s tool descriptions, parameter descriptions, and annotations actually say. Anthropic’s guidance: write descriptions in third person, be specific, include key terms and explicit triggers. There is also a soft ceiling: Anthropic’s tool search documentation notes that selection accuracy degrades significantly past 30 to 50 available tools, which favours lean, well-described tool sets over sprawling ones. This is positioning copy written for an LLM reader. The product team that controls it controls the strongest cold-start lever.
  3. Usage (the compounding lever). Once ranking kicks in, it is usage-based. (Anthropic’s own connector directory docs: “Ranking is usage-based, similar to other app stores.”) The first connectors with real adoption velocity get a structural advantage that is hard to claw back, because their ranking position compounds whether competitors are vetted into the directory or not. This is the chicken-and-egg problem early App Store entrants faced, with the same operating implication: get in early, drive real activations, and the flywheel does the rest.

There is no paid catch-up path. There is no bid for placement, at least not yet. The competitive moat moves from advertising budget to operational discipline: directory submission, metadata quality, and adoption velocity. The companies that recognise this as a distribution channel and build for it explicitly will not be visible to their competitors until the rankings settle. By then it is late.

For service businesses, this rewrites the CAC stack. Every previous distribution channel had a paid acquisition line: SEM bids, social ad budgets, affiliate placements, comparison-site rev shares. The Claude surface has none of that today. The line items are submission to the directory, ongoing metadata work, and the activation velocity of real users. For services that have spent the last decade fighting CAC inflation in search and social, that is a structurally different unit economic, and a meaningful one. The companies that get in early do not have to outspend competitors; they have to out-describe and out-activate them.

This is exactly what we build for at WaniWani. Submission engineering, metadata craft tuned to the model’s reading, and full-funnel analytics for the activation flywheel. The discipline is new. The operating playbook for it does not exist yet outside a handful of teams. We are one of them.

What this means for your service business

Should we be on Claude connectors now, or wait?

Build now. The mechanic is already eighteen months mature. It shipped for developers in November 2024 and has been load-tested on Claude Code, the most-used agentic coding tool of 2026, ever since. Ranking is usage-based, which means early entrants compound their position over time. Service categories (insurance, banking, broadband, mortgages) are being actively onboarded in 2026. Waiting gives competitors a usage signal lead that is hard to close once it exists.

How does Claude decide which connector to suggest?

Two documented signals: your metadata and your usage. When a user asks something inside Claude, the model reads your connector’s name, tool descriptions, parameter descriptions, and annotations to decide whether your service fits the conversation. That is the cold-start lever. Once your connector starts seeing activity, Anthropic’s documentation states ranking is “usage-based, similar to other app stores” (claude.com/docs/connectors/directory). So metadata wins you the first conversation; usage compounds you into the rank-1 slot.

Can we pay to be top-ranked in the Claude directory?

No. Anthropic has publicly committed to keeping the surface ad-free: “There are no paid placements or sponsored answers in conversations with Claude.” (Anthropic blog, April 23, 2026) Unlike Google Search, app stores, or affiliate networks, there is no bid for placement and no sponsored slot. The levers are directory inclusion, metadata quality, and the activation velocity of real users. That is a structurally different CAC stack from any previous distribution channel.

Why does this matter more for services than for products?

Services are conversation-led, personalized, and high-intent. Commodity products fit a search-and-click stack: the buyer knows what they want and picks from a list. Services do not work that way. The buyer is describing a situation, not naming a SKU, and expecting an answer specific to them. That is exactly the conversation Claude’s connector surface is designed to handle. Search and app stores were built for commodity products. Recommendation engines like Claude are a better structural fit for how services actually sell.

What is the difference between getting on Claude versus ChatGPT?

On ChatGPT, the user picks the app (for now). On Claude, the model picks for the user. ChatGPT’s apps live in a store-style surface: users browse, install, and invoke. Claude’s connectors are surfaced by the model based on the conversation, without the user necessarily browsing the directory. The same MCP server can technically run on both, but it needs to be optimized differently for each. Both surfaces are evolving and will continue to converge and diverge, which is why instrumenting both is the durable position.

What is the first thing we should actually do?

Submit your distribution MCP server to the Anthropic Connectors Directory and treat the metadata as positioning copy. Submission is the gate. The directory listing is the prerequisite to being model-suggested to anyone outside your own account. Once accepted, the name, descriptions, and parameter docs of your tools are what the model reads when deciding whether to surface you. Have the person who owns brand positioning own that metadata. Revise it the way you would revise a high-traffic landing page. (At WaniWani we run this end-to-end for service categories where the metadata, compliance, and analytics need to clear regulated review.)

What this means about the future

For services, the audience math changed alongside the platform. A year ago, building on Claude meant reaching mostly developers, knowledge workers, and a small power-user consumer base. Today the audience is mainstream and growing fast. The connector directory grew from roughly 200 entries at the April 23 launch to 375 by May 9, 2026 (community index). Service categories that have not yet been onboarded (insurance, banking, broadband, mortgages, energy) will arrive into a directory where the earliest entrants in their category already have eighteen months of usage signal compounding.

The trajectory from here, on the evidence available:

  • More categories ship. Each new service category enters a directory that already has a ranking flywheel running for the first movers. Whether you are in that first-mover cohort is a 2026 decision, not a 2027 one.
  • Commerce primitives likely arrive. As more consumer transactions move through Claude, the pressure to introduce payment middleware or revenue-share structures will grow. The ad-free commitment may survive; some form of monetization probably emerges in time. The early-mover cohort gets to build a usage position before that overlay exists.
  • The platforms partly converge. ChatGPT’s apps surface keeps moving toward model-driven suggestion. Some patterns will look similar across both. But the cultural defaults, coding heritage versus consumer-store heritage, will keep the surfaces meaningfully distinct for the next several years. Optimizing across both is a real engineering decision, not a copy-paste.

The strategic implication: the platform that many service businesses ignored as a dev tool in 2024 is the consumer distribution channel they cannot afford to ignore in 2026. Services that treat April 23 as a feature update will look up in eighteen months and find that competitors they have never seen are sitting at rank-1 on the conversation surface that matters most to them.

At WaniWani, this is the work. We deploy services into the Claude and ChatGPT directories, run metadata as positioning copy, track ranking shifts as the surfaces evolve, and keep the distribution stack compliant for regulated categories. If you sell a service through AI and you are still treating April 23 as a feature update, the call worth booking is the one where someone shows you what your own brand is doing in a Claude conversation today.

References

WaniWani builds AI distribution infrastructure for companies selling through ChatGPT, Claude, and Gemini. We deploy your AI app on the MCP protocol, monitor how AI surfacesi your brand across platforms, and keep your distribution compliant as regulations evolve. Learn more at waniwani.ai.

← Back to all posts