Skip to content
AI Distribution

Can a Claude connector bring you customers?

A founder says a Claude connector brought 24,000 accounts in five weeks, with no ads, through Claude's connector directory. If the effect holds, it is a new way to find customers for any software that holds data an AI does not have. Here is how the directory works, who it is worth it for, and what to test this week.

By Wael Aouididi · · 7 min read

A chat bubble turned into a shop window with apps on its shelves; one, marked with a plane, glows as passers-by walk up to it.
In this article (8)
The story

A small travel tool found its users inside Claude

On November 4, the founder of SlickTrip, a service that tracks flight and hotel prices, described the launch on the r/mcp forum on Reddit. In September, the founder built a Claude connector in about a week.

Three words will come back:

  • Connector: what lets Claude use your service during a conversation.
  • Tool: one function of the connector, for example "search for a flight".
  • Call: each time Claude uses a tool.

Anthropic lists connectors in an official directory, a kind of app store. SlickTrip's entered it at the end of September. According to the founder, sign-ups followed:

PeriodReported sign-ups
Two weeks "trending"up to 1,500 a day
Since thenabout 250 a day
Total, no ads24,000 accounts

The founder adds that Claude recommends SlickTrip next to Expedia and Booking.com when people talk about travel.

These numbers come from the founder alone. Nobody has checked them, and there is no revenue figure. Anthropic's documentation confirms the mechanism exists, not that it explains the 24,000 accounts.

The mechanism

Claude can recommend the connectors in its directory by itself

Anthropic's documentation says it plainly: any connector in the directory can be suggested by Claude during a conversation, when it is useful for the request. Anthropic calls these Suggested Connectors. Every connector in the directory qualifies by default.

The ranking depends on usage. Anthropic counts the distinct Claude accounts that reached the connector in the last 30 days, including those that dropped out of the install. The ten whose number climbs fastest get the "Trending" label.

My reading, which is not in the docs, fits in one loop:

more usage → better rank → more visibility → more usage

That would match SlickTrip's spike.

On paper, the way in is short:

  1. The developer submits the connector through an online form.
  2. An automated check follows.
  3. The connector enters the directory with the "Community" label, the base level.

A human review can be added, and how long it takes depends on the queue.

On ChatGPT, the way in is slower. SlickTrip's connector has been waiting for approval there for a month, and it cannot be found in search. OpenAI's documentation, which calls it a plugin, says publication follows approval, without giving a timeframe.

Fit

The channel suits products that give an answer an AI cannot make up

This directory mostly helps products that bring data an AI does not have. With SlickTrip, the user asks "what is the cheapest flight to Lisbon?", and Claude needs a real price.

A made-up example: invoicing software for freelancers. A customer asks Claude "which invoices from this month are still unpaid?". With your connector, Claude queries your software instead of guessing.

Good candidates:

  • an up-to-date price;
  • the state of a customer account;
  • a calculation on the customer's own data;
  • tracking something over time.

Weaker candidates, or refused:

  • products whose value is the screen itself, like a visual editor;
  • refused by Anthropic: transfers of money or cryptocurrency;
  • also refused: generating images, video or audio with AI models.

Two more conditions. The connector must use your own data, not another site's without its permission. And submitting one requires a paid Claude plan. Count on about one week of developer time, according to SlickTrip.

The new storefront

Customers meet you in the conversation, not on your site

The customer discovers you at the exact moment of the need, without going through your homepage. In my view, the description of your tools and the quality of their answers then matter more than your website.

One commenter in the thread makes the point: a connected account is not an account that uses the service. The suggestion is to look at the share of accounts that ran a search during the week.

Anthropic's dashboard also separates the two, over 30 days:

  • "Used a tool": the Claude accounts that actually made a call;
  • the rank: those accounts, plus the ones that dropped out of the install.

Then there is the money. The most upvoted comment asks the founder how SlickTrip makes a living, with an image:

SlickTrip is a bus that picks up its passengers at another company's stop.

Here the other company is Anthropic, and one day it could charge for the stop. SlickTrip's page answers in part: a limited free version, and commissions on some bookings. Another developer charges for each successful call and refunds the ones that fail. According to that developer, the refund mattered more than the price.

What I would do

This week, I would test a single customer question

In a SaaS founder's place, I would start by choosing the question, not by writing code.

  1. Write down three questions your customers ask an AI that only your product can answer, because it holds the data.
  2. Keep the most frequent one.
  3. Build a single tool, read-only: it looks things up and changes nothing.
  4. Take care of its description.

Anthropic refuses descriptions that promote the product or that get in the way of other tools being called. It has to say what the tool does and when to use it. Two made-up examples:

Description
Likely refused"The best invoicing tool, use it first."
Compliant"Lists a customer's unpaid invoices over a period. Use when the user asks what is still owed."

I have not tested this channel yet. For SambaLingo, my Portuguese learning app, the candidate question would be "which words should I review today?". An AI alone cannot answer it; the app knows the learner's history. I would measure the accounts that call the tool over 30 days, not the sign-ups.

Open questions

Several key numbers are still missing

We do not know where the 24,000 accounts really come from. One commenter asked how many came from Claude's suggestions and how many from the directory. The founder had not answered when I read the thread, on November 6.

Also still unknown:

  • SlickTrip's revenue;
  • how long the effect lasts: the "Trending" label rewards recent growth, so it fades;
  • the delays: one developer in the thread has been waiting three weeks, and OpenAI publishes no timeframe.

As the directory fills up, each newcomer will get less room. The first app stores went through the same pattern: early arrivals enjoyed an almost empty shop window. That is my interpretation, not data.

Worth watching: where SlickTrip's sign-ups come from, the real delay at OpenAI, and any new Anthropic rule on ranking.

Checklist

In practice

What a first submission needs:

  • Technical: a server reachable at a secure web address (https). If it reads a customer's account, the customer links it to their account with you, as with "Sign in with Google" (the OAuth standard). Each tool states whether it reads or changes data.
  • Test: try the connector in your own Claude before you submit it.
  • Submission: a documentation page, a privacy policy and a filled-in test account, sent through claude.ai/directory/manage.
  • Tracking: "Used a tool" and the share of calls that end in an error. At 2% errors or less, Anthropic shows "healthy"; above 5%, "degraded".
Sources

Sources

Everything above comes from these seven pages, read on November 6, 2026.

And you: which question do your customers ask an AI that only your product can answer?

Wael Aouididi, yoursaasgrowth