Resources · Claude connector

Claude Turo connectorWhat Claude searches in Turo's car listings.

The Claude Turo connector exposes 1 tool: 1 read, 0 write, 0 undocumented. It searches cars available on Turo for a place and dates, with pricing, ratings and availability, and lets you refine in conversation. Booking and payment stay in Turo's app or website.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can search Turo

With this connector, you describe the trip to Claude in plain words, where, when and what kind of vehicle, and it runs a search across the cars available on Turo while it answers. Turo's help article adds that you can keep the conversation going to narrow the results.

A car that fits the trip. You describe the vehicle you need, such as an SUV or a convertible, and search_vehicles returns available listings with pricing, ratings and availability for your dates.

Refining without starting over. Turo's help article says you can keep the conversation going to adjust on price, vehicle characteristics or pickup and return location, so a second question tightens the first answer.

A clear answer when nothing matches. If the search comes back empty, Turo tells the model to say that nothing matched, allows at most one automatic retry, then has it ask which suggestion you prefer.

What it will not do: Claude does not book, pay or manage the trip. Turo says those steps happen in its app or on its website once you pick a listing. The search only covers the countries Turo lists, and nothing runs on its own: Claude calls the tool only while it answers you. Automation platforms, which run on a schedule, are a different job; our Integrations hub lists the ones we document.

Vocabulary

Five words to read first

The vocabulary Claude uses around this connector, kept short.

Connector
A link you set up once between Claude and an outside service, which Claude then calls on while it answers you.
Tool
A named capability a connector hands to Claude. Turo exposes exactly one, and the directory sheet lists it by that name.
Authorization
The sign-in or consent screen a service may show when you connect, where you grant the access Claude uses. Per person, revocable.
Approval
The confirmation Claude waits for before it changes something in an account for you, shown in the chat when it matters.
MCP
The common standard connectors rely on: it is what lets an assistant like Claude query an outside service such as Turo.
Connect

Connect Turo to Claude in three steps

  1. 01

    Find Turo among the connectors

    Open Claude's settings, go to Customize, then Connectors, and search for Turo. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can connect.

  2. 02

    Connect it

    Click Connect on the Turo row and follow any window that opens. If a screen asks for consent, it belongs to the service, not to Claude. If the link breaks later, Disconnect it and connect it again.

  3. 03

    Turn it on in the chat

    Turo's own instructions add one step: go back to the conversation and make sure the Turo connector is enabled there, then ask Claude to use it to find a vehicle for your trip, with place, dates and needs.

Tools

The single tool, and what it covers

Turo gives Claude 1 tool: 1 that read your account, 0 that change something in it.

One tool, and it reads. Turo describes it in its own tool description and help article, and its name stays as Claude shows it.

  • 1 read

What Claude reads (1)

1 tool

One search across Turo's available cars, with no booking step.

search_vehicles

Searches cars available on Turo with filters on location, date range, vehicle preferences and sort order, and returns each listing with pricing, ratings and availability.

When it helps
you know where and when you need a car and want to see the available listings and their prices before you open the app.
Watch out
Turo instructs the model not to run a search in a place where it does not operate.

Sourcemcp.turo.com · October 1, 2026 ↗

Approvals

What Claude asks before acting

Claude's default is to stop and ask before any action it takes on an account for you. The only Turo tool searches listings, so a normal session has nothing to confirm, and booking happens outside Claude.

On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked each time. They can also restrict what a connector may do for the whole organization, such as allowing reads and closing writes, and no member overrides that from their own account. Claude works with the rights of whoever connected it, nothing more. The official read or write label per tool is visible only in a connected account's settings.

Plans

Plans: the general rule

Not one of the 819 sheets in the official directory shows plan availability. For an individual connector, that information is not published anywhere.

Anthropic publishes a general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables a connector before members can connect it. The publisher's help article names plans for this one, and that statement sits in the conflict below. The directory sheet shows its current state for you.

Limits

Where the Claude Turo connector stops

A connector is not an automation. Claude searches Turo while it answers you; nothing fires when a new car appears or a price changes.

A list of read-only tools is an observed floor, not a guarantee: an admin can open actions no public sheet shows. The verification badge is not a security audit, and Anthropic states on every sheet that it does not pick a publisher's tools. This connector is documented only by Turo, through its help article and its tool description; no Claude help article or Anthropic developer page covers it, so treat the details as the publisher's word.

Two official sources disagree

Which Claude plans can use the Turo connector?

What this page followsNeither is marked out of date, and they do not say the same thing. Anthropic's rule covers every connector; Turo's note is narrower but comes from the publisher. Check the connector's directory sheet from your own account before you rely on either.

Need help

Need help connecting Turo to Claude?

A person reads every message.

FAQ

Questions about the Claude Turo connector

01What can Claude do with the Turo connector?
Claude can search cars available on Turo while it answers you. Its single tool filters by location, dates, vehicle preferences and sort order, and returns listings with pricing, ratings and availability. Turo's help article suggests giving the trip location, the dates and what you need from the vehicle, then continuing the conversation to refine on price, vehicle characteristics or pickup and return location. Results stay within the countries Turo serves.
02Can Claude book or pay for a Turo car?
No source describes that, and Turo says the opposite. Its help article states that booking, payment and trip management happen in the Turo app or on the website after you select a listing. The directory sheet lists one tool, a search, which Turo marks as read-only. A read-only list is what the public sheet shows today; an admin can open actions that no public page displays, so check the sheet if it changes.
03Does Claude ask before searching Turo?
Claude's default is to ask for confirmation before any action it takes on an account for you. The Turo tool only searches listings, so a normal session has nothing to confirm. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a new prompt, and they can restrict the connector for everyone. No source describes an approval step specific to this tool, and the booking itself, the one step with money involved, happens in Turo's app or website rather than in the chat.
04Which Claude plans include the Turo connector?
No official source publishes plan availability per connector, and none of the 819 directory sheets shows it. Anthropic's general rule opens remote connectors to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Turo's help article gives a narrower list of plans; both versions sit side by side in the limits section. Check the connector's directory sheet from your account.
05Does Claude see my Turo account or past trips?
No source describes that. The only documented tool searches cars available on Turo, and Turo's help article describes searching and discovering vehicles, not reading a profile, past trips or messages. Trip management happens in Turo's app or website. As a general rule, Claude reaches only what the person who connected it can reach, and an owner on Team or Enterprise can restrict the connector for the whole organization. For anything about an existing trip, open the Turo app.
06Why does Claude refuse to search Turo in some cities?
Because Turo tells it to. The tool description says Turo operates only in the United States, Australia, France, the United Kingdom and Canada, and in Canada only in listed provinces plus Yukon. For an unsupported country, the model is told to say so and offer a supported one; for an unsupported area inside a covered country, to suggest the closest supported places. It is told not to run the search at all.
07Claude or an automation tool for Turo?
They solve different problems, so choose by task, not by ranking. Claude fits a trip you plan in conversation: describing what you need, comparing a few cars, refining the search, with the tool called only while it answers. An automation platform fits repeated jobs that run without you on a schedule. This connector schedules nothing and watches nothing in the background, and booking still happens in Turo's app or website whichever route you take.