- Home
- Resources
- Integrations
- CarGurus
Claude CarGurus connectorWhat Claude can do in your CarGurus account.
The Claude CarGurus connector exposes 2 tools, both read, 0 write. One searches listings, the other opens a single car in detail. Below: what Claude finds for you, what it never touches, who can switch it off, and where the US-only limit bites.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug CarGurus into Claude
Car shopping usually means a dozen filters and twenty browser tabs. With the connector, you describe the car you need in plain words (a budget, a model, a family of five, snowy winters) and Claude runs the search on CarGurus for you, then talks you through what came back. You stay in one conversation instead of juggling a listings site and your notes.
A shortlist from a vague brief. You say you need something safe in the snow for under a set budget near a US city. vehicle-listing-search pulls matching listings, and Claude explains why each one fits or doesn't.
The full picture on one car. One listing catches your eye. vehicle-listing-detail brings back that car's specs, safety information and dealer details, so you can compare two finalists side by side in the chat.
A second opinion before the dealer visit. You paste the trims you are hesitating between and ask Claude to line up the differences that came back from CarGurus, so you walk in with sharper questions.
What it won't do: reserve a car, message a dealer, save a favorite or change anything on CarGurus. The publisher calls it strictly read-only, and its directory sheet only lists reading tools. It also covers US listings only, and nothing runs on its own: no alert fires when a new car matches your search. That kind of background watch is an automation job, a different trade; the Integrations hub gathers that side of things.
The vocabulary in one minute
Five words you will meet while plugging in CarGurus.
- Connector
- The link you set up once between Claude and a service, so Claude can work with it while it answers you in the chat.
- Tool
- One named job the connector lets Claude do. Claude picks the tools it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, revocable the same way.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect CarGurus to Claude in three steps
- 01
Find CarGurus in Claude
In Claude's settings, open Customize, then Connectors, and look for CarGurus in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to turn the connector on before each member can link it.
- 02
Start the connection
Click Connect on its row and follow the window the service opens. If the link ever breaks, use Disconnect and plug it back in; access can also be withdrawn from the service's side.
- 03
Read the authorization screen
Read the screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. It can sometimes list wider permissions than what Claude does day to day.
The 2 tools, sorted by what they do
CarGurus gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Both tools read public listings. The names stay in English, exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsTwo tools that look up public CarGurus listings and change nothing.
vehicle-listing-detail
Opens one specific car and brings its full record into the conversation: specifications, safety information and the dealer selling it. Claude can then reason about that single vehicle instead of a list.
vehicle-listing-search
Turns your description into a CarGurus search, whether you give hard criteria like price, make or mileage, or a looser need such as a reliable commuter car. It returns the matching listings.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. Here, both tools only read public listings, so there is no change to confirm.
CarGurus's own article adds one thing: if Claude asks permission to use CarGurus, answer yes. On Team and Enterprise, owners decide whether members may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, and nobody overrides that from their own account. Finally, Claude works with the rights of the person connected and nothing more.
Which plans it's available on
None of the 819 sheets in the official directory shows plan availability. The answer for one connector is published nowhere: that is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can link it. For the current state, check the connector's own sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, and nothing starts by itself when a price drops or a new car is listed.
Everything here comes from the publisher: no Claude help article covers CarGurus. A tool list that only shows reading is an observed floor, not a guarantee, since an admin can open actions no public sheet mentions; by default, this sheet exposes reading only. The directory badge is not a security audit either, and Anthropic says on every sheet that it doesn't control the tools a publisher exposes. The same questions are answered, tool by tool, on the Claude affinity connector page.
Need help connecting CarGurus to Claude?
A person reads every message.