50% off your first year. Join before 2027. Claim →

Claude connector search: how an MCP gets found

Claude connector search: how an MCP gets found

In the previous article on the Claude Marketplace we talked about Claude suggesting connectors when one fits the task. Now we want to dive deeper into Claude connector search through one example: SlickTrip MCP, a flight and hotel price tracker.

The research was inspired by the Reddit post “Claude brought us 24,000+ users in 5 weeks”. SlickTrip’s founder claimed 24,000 new accounts with no ads after the connector went live in Claude’s directory at the end of September: up to 1,500 sign-ups a day while it was trending, and about 250 a day since. The founder credits the listing: “When someone asks Claude about flights or hotels, it recommends us right next to Expedia and Booking.com.” We cannot confirm the sign-up numbers, but we could test how the connector gets found. We sent about 500 prompts (some of them more than once) to real claude.ai chats on Opus 5.5 with web search on, which gave 348 connector registry searches, and compared what came back with SlickTrip’s public directory listing.

Key takeaways

  • SlickTrip was returned in 44 of 348 registry searches, and Claude never searched for its name. It was found through generic travel words such as flights and hotels.
  • The search matches the directory listing: name, one-liner and tool names. A keyword has to appear there as a whole phrase, words together and in order.
  • Words found only in SlickTrip’s live MCP tool descriptions did not get it returned.
  • Being returned is not being suggested. Claude picks a few connectors from the results for its “Connectors that could help” card.
  • Claude searches connectors when a task needs a specific system that holds the user’s data or does the action, and searches the web when the answer is public information.
  • Only partner and Anthropic tier connectors came back, never community tier.

How Claude searches for connectors

SlickTrip’s one-liner reads: “Search flights, hotels and seats, then get alerted the moment a price drops.” The listing has 36 tools, including search_flights, search_hotels, price_calendar, hotel_price_calendar, seat_availability, track_flight, track_hotel, track_seats, update_flight_tracking, hotel_booking_options, route_airlines and recent_deals.

SlickTrip's listing in the Claude connector directory: the name, the one-liner "Search flights, hotels and seats, then get alerted the moment a price drops.", the full description and example prompts such as "Find me flights from New York to Los Angeles on November 19"

For each prompt Claude sends the search a handful of keywords. Here are examples from our chats, each with the keyword that matched SlickTrip’s listing:

  • flights, flight search, travel booking, airfare: flights is in the one-liner (“Search flights, hotels and seats”).
  • american airlines, flight seat map, airline booking, flights: flights again. None of the seat keywords is in the listing as a phrase.
  • vacation rental, airbnb, vrbo, travel booking, hotels: hotels is in the one-liner.
  • price alerts, price tracker, price drop, camelcamelcamel, keepa, shopping deals: price drop matches “price drops” in the one-liner.
  • hotel booking, booking.com, expedia, travel: hotel booking is inside the tool name hotel_booking_options.
  • seat alert, flight seat map, expertflyer, british airways, flight tracking: flight tracking is inside the tool name update_flight_tracking.

Every chat whose keywords included flights returned SlickTrip, 30 of 30. Across all searches, flights accounted for 31 of its 44 returns and hotels for 5.

Claude never sent slicktrip as a keyword, unlike popular brands such as expedia, kayak and booking.com, which it added to its searches on its own.

SlickTrip ranked between 2 and 10 in the results, with a median of 5 for one-liner matches and 8 for tool name matches. (That is its position in one search’s results, not the usage-based directory rank.) It never ranked first, because nobody searched for its name.

Four parts of a listing that impact the search ranking:

  1. Name. A brand keyword puts the connector at rank 1 or 2. Names are also matched word by word and fuzzily: a finance connector whose name resembles the word “flights” came back in most of our flight searches.
  2. One-liner and tool names. The whole keyword must appear as a phrase, words together and in order. Tool names are split on underscores, so update_flight_tracking reads as “update flight tracking”. The last word may run on into a plural (price drop matches “price drops”), but not the reverse. These matches rank 2 to 10.
  3. Description. Phrase matches here count only weakly: 71 of the 3,164 results returned across all our chats.
  4. Tier. Every result was partner or Anthropic tier. The search never returned a community connector, even when its listing matched the keywords.

How Claude decides which connectors to display

A phrase match does not guarantee a place, since a crowded list of 10 or more results can push a weaker match out. The directory’s public search API splits keywords into words in every field and returns more than Claude’s search does, so treat it as an upper bound.

SlickTrip was in the results in 42 chats, and the same travel connectors came back with it almost every time: Expedia in 38 of those chats, eDreams in 36, lastminute.com in 33, Turkish Airlines in 29, plus a few others. Claude then chose which ones to show on the card:

ConnectorOn the card (of 42 chats)
Expedia30
SlickTrip18
lastminute.com18
eDreams11
Booking.com3

On 8 of its 18 cards, SlickTrip was the only connector. All 8 were tasks only its tools cover: open seats on a specific flight, fare and price alerts, price drops. “Which seats are still open on AA100 from New York to London on December 3?” ran 3 times, with SlickTrip alone on the card each time.

Hotels were harder. For “Find boutique hotels in Lisbon with free cancellation…” Claude searched hotel booking, booking.com, expedia, travel. SlickTrip came back at rank 8, but the card showed Expedia and Booking.com.

The search reads the directory listing, not your live server

The keywords seat alerts and flight seat alert never returned SlickTrip, although “seats” is in its one-liner and tool names. Neither exact phrase is in the listing. The prompt “What seat alerts do I have?” got no suggestion at all.

“Seat alerts” does appear in SlickTrip’s live MCP tool descriptions, which its server sends to a connected agent. It still did not retrieve SlickTrip, and that search returned only 8 results, so nothing was crowded out. It is one clean case for SlickTrip, consistent with the other connectors we checked.

The same need in other words worked: “Alert me when an aisle seat opens up on BA 178 from JFK to Heathrow on February 9.” Claude’s keywords included flight tracking, which is inside the tool name update_flight_tracking. SlickTrip came back at rank 2 and was the only connector on the card.

Does Claude search connectors or the web?

Claude can search the connector registry, the web, both or neither. Across all chats:

OutcomeShare of chats
Web search only35%
Connector registry search only28%
Both19%
Neither18%

The intent of the prompt decides which:

Prompt intentChatsConnector searchWeb search
Concrete travel search (route and dates, a seat on a flight)4372%49%
Flexible travel (“cheapest days to fly”, “deals”, “where can I go”)258%92%
Alert, watch or track a price or seat3432%18%
Acting on “my” account or data7489%3%
Hire an individual freelancer or gig worker18375%54%
Find an agency, company or firm20822%78%
Reputation of a company or seller2910%100%
Follow-up to a chat that does not exist (“the second hotel”)3318%6%

Claude searches connectors when the task needs a specific system that holds the user’s data or performs the action, and searches the web when the answer is public information. A route on a date needs a booking tool. A question about the cheapest week or the best deals reads as public research. That is awkward for SlickTrip: its price_calendar tool answers “cheapest days to fly”, yet that kind of flexible question went to the web 92% of the time, so the connector was rarely considered.

Alerts are a case of their own. In 13 chats, Claude created or listed its own scheduled task instead of searching for a connector.

Do longer prompts go to the web?

Longer prompts did not reduce connector searches:

Prompt lengthChatsConnector searchWeb search
0–7 words6641%36%
8–11 words33950%58%
12–15 words20345%54%
16+ words9846%51%

How stable is it?

We ran 165 prompts more than once. The connector search came out the same in 84% of them, the web search in 83%. Prompts acting on the user’s own account never changed: 21 of 21 had the same outcome on every repeat.

Check your keywords and tool names with the Online MCP Inspector

The free Online MCP Inspector runs in your browser. Paste your remote MCP server’s URL and it lists your tools, prompts and resources in plain language, with each tool’s title and name. You can also run a tool and test OAuth sign-in. Then read your tools the way the search does:

  1. Remove the underscores and read each tool name as a phrase: hotel_booking_options becomes “hotel booking options”.
  2. List the keywords people and Claude use for your category. In travel: flights, flight search, hotel booking.
  3. Check whether each keyword appears, whole and in order, in a tool name or your one-liner.
  4. Repeat for a competitor’s public server. Some servers ask you to sign in before they list their tools.

The Inspector shows your live server, while Claude’s search reads your directory listing. When you rename a tool, update the listing too. Our guide to getting listed in the Claude Marketplace covers the portal where you manage it.

Conclusion

SlickTrip gets found without anyone asking for it by name, because the words in its listing match the words Claude searches with. flights in its one-liner put it in the results of every chat that used the keyword, and “seat alerts” in its live tool descriptions never did. Compare your own listing with the keywords your users type.

Open the Online MCP Inspector and read your tool names the way Claude’s connector search does.

Similar articles

ChatGPT plugin directory: a new growth channel

The ChatGPT plugin directory gives an MCP server something it never had before: a listing in front of ChatGPT users, reviewed by OpenAI and backed by a model that decides when to call it. I think this…

Read article: ChatGPT plugin directory: a new growth channel
Claude Marketplace: a new MCP growth channel

Claude Marketplace: a new MCP growth channel

The Claude Marketplace is where Claude users find connectors, and for a team that ships an MCP server it looks a lot like the early App Store: a catalog that lives inside the product people already…

Read article: Claude Marketplace: a new MCP growth channel

Gemini Connected Apps: a new MCP growth channel

Gemini Connected Apps let an MCP server work inside the Gemini app and Google Search, and on October 28, 2026 Google opened the program to more developers with the Connected Apps Platform. For a team…

Read article: Gemini Connected Apps: a new MCP growth channel

Grok Bot Marketplace: a new MCP growth channel

The Grok Bot Marketplace is xAI's new way to get a plugin or MCP server in front of Grok Bot and Cursor users, with Grok itself listed as coming soon. One form on xAI's site covers all three. In this…

Read article: Grok Bot Marketplace: a new MCP growth channel

Muse connectors: a new MCP growth channel

Muse connectors let Meta's personal AI agent use your product while it works on a user's task. If your team ships an MCP server, Meta's new Muse Connector Platform gives it one more place to be found…

Read article: Muse connectors: a new MCP growth channel

Official MCP Registry: a new MCP growth channel

The official MCP Registry is the one place where you publish your MCP server's metadata and let other catalogs pick it up. Before it existed, every directory had its own submission form, pull request…

Read article: Official MCP Registry: a new MCP growth channel

Perplexity connectors: a new MCP growth channel

Perplexity connectors let Perplexity search, read and act in other products on a user's behalf, and the remote ones run on the Model Context Protocol. For a team that ships an MCP server, that makes…

Read article: Perplexity connectors: a new MCP growth channel

How to publish an MCP server to the MCP Registry

To publish an MCP server to the official MCP Registry, you describe it in a server.json file, prove that you own its namespace, and push the file with the mcp-publisher CLI. There is no form and no…

Read article: How to publish an MCP server to the MCP Registry

How to submit an MCP to Gemini

To submit an app to Gemini, you register your remote MCP server as a Connected App in the Google Connected Console, test it with Gmail accounts, send it for review and then publish it yourself. This…

Read article: How to submit an MCP to Gemini

How to submit a connector to Claude

To submit a connector to Claude, you send your remote MCP server to Anthropic's Connectors Directory from the developer portal, answer a review, and then publish the approved listing yourself. This…

Read article: How to submit a connector to Claude

How to publish an MCP to Muse

To submit a connector to Muse, you sign in to Meta's Muse Connector Platform, describe your MCP server and your business, hand over credentials and a test account, and wait while Meta reviews every…

Read article: How to publish an MCP to Muse

How to publish an MCP in Perplexity

To submit a connector to Perplexity, you send a connector proposal through a Google Form, and Perplexity's Plugins marketplace team decides whether to take it further. The help center documents no…

Read article: How to publish an MCP in Perplexity

How to submit a plugin to ChatGPT

To submit a plugin to ChatGPT, you upload a ZIP bundle to OpenAI's plugin portal, connect a remote MCP server that anyone on the internet can reach, and wait for review. A first review takes months…

Read article: How to submit a plugin to ChatGPT

How to submit a plugin to Grok

To submit a plugin to Grok, you fill in one short form on xAI's site. It asks for your MCP server URL or a public GitHub repository, a description, testing instructions and the places you want to be…

Read article: How to submit a plugin to Grok