Claude Shipt connectorWhat Claude can do in your Shipt account.
The Claude Shipt connector exposes 2 tools. 1 reads a store's products, 1 changes your Shipt cart, 0 are undocumented. Below: what Claude searches, what it puts in the cart, what it asks first, and what you still finish in Shipt.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can shop on Shipt
You say what you need in the conversation, and Claude turns it into a cart at a Shipt retailer. Search results show up in a panel inside the chat rather than as a list Claude writes out. Payment and the delivery window are not handled in the conversation: you open the cart in Shipt and finish there.
A cart built over the conversation. With Shop, Claude sets the delivery address, selects a retailer, searches for products and manages the cart across several messages, so the list can change as you go.
Looking before adding. Browse searches products at the store you already selected, or at another store without switching your session, so you can look at options before anything lands in the cart.
Starting over. Shop can also empty the whole cart in one go, and Shipt describes that as immediate. Changing retailer works the other way: Shipt says the cart persists and items are not cleared when you switch store.
What Claude does not do: it does not pay, does not choose your delivery window and does not place the order; Shipt keeps those steps in its own app. Nothing runs in the background either, and Claude acts only while it answers you. A job that must start on its own belongs to automation tools, a different trade; the Integrations hub covers that side.
Five terms before you start
The words you will meet while plugging Shipt into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- Shipt's own sign-in screen, where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before going through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Shipt.
Plug Shipt into Claude in three steps
- 01
Find Shipt among your connectors
In Claude's settings, open Customize, then Connectors, and look for Shipt. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first before each member can sign in.
- 02
Start the connection
Click Connect on Shipt's row and sign in through the window Shipt opens itself. If the link ever breaks, the fix is to use Disconnect, then plug Shipt back in from that same row.
- 03
Read the authorization screen
Check Shipt's authorization screen before you accept. It belongs to Shipt, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Shipt account.
The 2 Shipt tools, sorted by what they do
Shipt gives Claude 2 tools: 1 that read your account, 1 that change something in it.
One tool looks at products, the other works on your cart. Names stay in English, as Claude displays them.
- 1 read
- 1 write
What Claude reads (1)
1 toolOne tool that searches a store's shelves without touching your cart.
Browse
Looks up products at the retailer picked for your session, relying on what Shipt has already stored for it. It can also look at a different store without changing the one you selected.
What Claude changes (1)
1 toolOne tool that sets your address and store and edits the cart. No source describes a confirmation specific to it: the general rule below applies.
Shop
Approval: see the ruleRuns the shopping session on Shipt: sets the delivery address, selects the retailer, searches items and manages the cart over several turns. It can also empty the cart entirely.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the conversation, at the moment it counts.
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, for example keeping reads and closing writes; nobody overrides that from their own account. Claude works with the Shipt account you sign in with and nothing more: what that account cannot reach, Claude cannot reach either.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer is published nowhere, connector by connector: a real gap in the catalogue, not in our research.
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 enables the connector for the organization before members can connect one by one. For Shipt's current status on your account, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing reorders by itself.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's verification badge is not a security audit; Anthropic states on every sheet that it neither chooses a publisher's tools nor guarantees how they behave. This connector is documented only by Shipt, through its page on AI shopping and the tool descriptions its own server publishes.
Need help connecting Shipt to Claude?
A person reads every message.
