Shipt

Build a same-day grocery cart.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Shipt connector does

The Shipt MCP server lets Claude, ChatGPT or any MCP-compatible agent find same-day delivery retailers, browse products and assemble a grocery cart. Two tools cover it. Neither buys anything: Shipt's own description says the cart is private and that you continue checkout in Shipt's shopping experience, which puts a person between the agent and your card.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Shipt tools (2)

  • Browse
  • Shop

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The connector does not complete a purchase, and that is its most important property. Shipt's own description ends the flow at a private cart and continues checkout in Shipt's experience. A person picks the delivery window and confirms. Credit this as a guardrail — but it does not stop an agent assembling a wrong cart that you then approve.
  • The documentation is a marketing page. shipt.com/ai is the URL Anthropic publishes as this connector's documentation and it names no tools, no schemas and no version. There is no developer documentation for this connector anywhere we could find. Every operational fact on this page comes from Shipt's general help centre, which never mentions the connector.
  • No annotations could be read. The endpoint refuses anonymous requests, so we could not confirm whether Shipt marks either tool readOnlyHint or destructiveHint. Treat both as unannotated for planning purposes, and note that Shop mutates cart state even though it cannot buy.
  • The directory record carries no permissions label at all — no key, not an empty one. A user at the consent screen for a commerce connector on a consumer account API is shown no summary of what it can reach.
  • The RFC 9728 descriptor is site-wide, not endpoint-specific. Only the root path form resolves; both nested forms return zero-byte 404s. Its resource names the API origin rather than the MCP endpoint, so the eight scopes describe the host's vocabulary and may not be what this connector requests. We did not begin an OAuth flow to find out.
  • The endpoint answers anonymous requests with 403 and no www-authenticate header. A client following RFC 9728 from the endpoint alone gets no pointer to the descriptor.
  • The final charge is not the checkout total. Shipt authorizes the order total plus a substitution allowance and settles on what was delivered, which can be higher with special requests or added items (Payments, fetched 2026-08-19).
  • Substitution decisions happen outside the agent's reach. They are chosen at Shipt's checkout, and the "Contact me" option routes a live question to the account holder's phone mid-shop. Shipt documents no agent participation in that exchange, and we found nothing describing what should happen when the ordering party is not a person at their phone.
  • Cancellation is app-only and the window is short — before the shopper starts shopping, after which Shipt directs you to support. No cancel tool exists in the listing. We give no consumer-rights advice and assert nothing about what any law requires.
  • Coverage is US-only and incomplete. Shipt states it does not operate in Alaska, Wyoming or West Virginia. Membership is $99/year or $10.99/month after a 14-day trial; guest shopping without an account is documented for ChatGPT only, not Claude.
  • The two-tool listing is unverified in both directions. We could not confirm it live, and Shipt publishes no tool documentation to check it against. Two is what Anthropic's snapshot records.

Frequently asked questions

Does the Shipt MCP server place a grocery order?

No. Shipt's directory description says the connector builds and edits a private cart and that you continue checkout in the Shipt shopping experience. The vendor's own three-step flow ends the same way — ask, let AI build your cart, then open your cart in Shipt, choose a delivery window and check out. The handoff is architectural, not a policy the model is asked to follow.

Can an AI agent spend my money through the Shipt connector?

Not through the connector itself. Checkout happens in Shipt's own app or website, where your saved card is charged, so a person selects a delivery window and confirms before any money moves. That gate does not depend on the model behaving correctly. The agent's reach ends at a cart that costs nothing until a human completes it.

Whose delivery address and payment card does Shipt use?

Yours, already stored on your Shipt account. Shipt accepts debit or credit cards in the app and states that all payments must be made there rather than by invoice. Addresses live on the account too, and you can save as many as you need. The OAuth descriptor requests read-only access to addresses, so the connector reads them rather than adding one.

How do I cancel a Shipt order an agent helped me build?

In the Shipt app, any time before your shopper starts shopping. Shipt documents tapping Orders, opening the order and choosing to cancel it; once shopping has begun you contact Shipt support instead. None of that is reachable through the connector, whose two tools cover browsing and cart building only. There is no cancel tool in the listing.

What happens if an item in an agent-built cart is out of stock?

Your substitution instructions decide, and you choose them at checkout in Shipt — not through the connector. Shipt documents three options: contact me, do not substitute, or choose a backup. The first has your shopper ask about every out-of-stock item. That conversation reaches the phone of the account holder, never the agent that assembled the cart.

Do I need a Shipt membership to use the MCP connector?

Claude requires a Shipt login, and Shipt sells membership at $99 a year or $10.99 a month after a 14-day trial. Guest shopping without an account is offered on ChatGPT only, per Shipt's own connection instructions. Shipt also states it does not operate in Alaska, Wyoming or West Virginia, so coverage is US-only and incomplete.

How many tools does the Shipt MCP server expose?

Two, named Browse and Shop in Anthropic's directory snapshot — the smallest partner-tier surface in this catalogue's commerce category. We could not confirm that live because the endpoint refuses anonymous requests. Shipt's marketing page documents no tool names at all, so there is nothing to check the listing against and no annotations to read.

Sources

  • Shipt, Shop Shipt with ChatGPT & Claude — https://www.shipt.com/ai (fetched 2026-08-19; the URL Anthropic's directory publishes as this connector's documentation. Source of the three-step ask/build/check-out flow, the open-your-cart-in-Shipt checkout statement, the send-it-to-Shipt statement, the Claude and ChatGPT connection instructions, the guest-mode-is-ChatGPT-only statement, the $99/year and $10.99/month membership prices with a 14-day trial, the student and SNAP EBT discount, and the Alaska/Wyoming/West Virginia exclusion. This is a marketing page and names no tools — see Limits) · retrieved 2026-08-19
  • Shipt help centre, Ordering — https://help.shipt.com/ordering (fetched 2026-08-19; source of the cancellation window and app steps, the support-line escalation once shopping has begun, the one-hour add-items window, the three substitution instruction options and their described behaviour, the backups mechanism, per-item notes, and the dietary-preference prioritisation. Individual articles render as accordions on this single URL rather than at separate addresses) · retrieved 2026-08-19
  • Shipt help centre, Payments — https://help.shipt.com/payments (fetched 2026-08-19; source of the debit-or-credit-card-in-app requirement, the no-invoice statement, the additional payment options in select metros, the temporary authorization plus substitution allowance, and the charge-for-what-you-received settlement behaviour) · retrieved 2026-08-19
  • Shipt help centre, Account — https://help.shipt.com/account (fetched 2026-08-19; source of the multiple-saved-delivery-addresses statement) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: a single anonymous POST to https://member-api.shipt.com/marketplace-mcp/v2.0/mcp returned HTTP 403 with a ten-byte plain-text body and no www-authenticate header; a GET returned the same, as did a retry with a browser user-agent. No credentials were supplied, no OAuth flow was begun, no tool on this server was invoked, and nothing was added to any cart at any point · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://member-api.shipt.com/.well-known/oauth-protected-resource (fetched 2026-08-19; the root form returns HTTP 200 with 239 bytes of JSON, while the path-append and path-insert forms both return zero-byte HTTP 404s. Source of the eight scopes, the single authorization server, and the site-wide resource value that names the API origin rather than the MCP endpoint) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://auth.shipt.com/.well-known/oauth-authorization-server (fetched 2026-08-19; source of the issuer, the authorization and token endpoints, the S256 and plain challenge methods, the advertised registration endpoint, and the device-code, token-exchange and refresh grants. The same document is served at the OIDC discovery path. Its scopes_supported omits the three read: scopes the resource descriptor advertises. https://member-api.shipt.com/.well-known/oauth-authorization-server returns a zero-byte HTTP 404) · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/8a9bc286-ea8a-45c8-8b9e-ccbde8297c5e (snapshot 2026-08-16; source of the two tool names, the partner tier, the streamable-HTTP transport, the endpoint, the client list, the empty prompt list, and the description field stating that the connector builds a private cart and continues checkout in Shipt's shopping experience. The record carries no permissions field; 465 of the 1,897 records in the snapshot do) · retrieved 2026-08-16
  • Shipt robots.txt — https://www.shipt.com/robots.txt (fetched 2026-08-19; allows all crawlers with per-extension allow rules, disallows the cart, checkout, account and substitution-preferences paths among others, and publishes three sitemaps. It carries no Content-Signal line, so no use-side restriction is expressed. No llms.txt exists — https://www.shipt.com/llms.txt returns the site's HTML 404 page, as does the .md suffix form of the documentation URL) · retrieved 2026-08-19
  • Shipt privacy policy — https://www.shipt.com/legal/privacy-policy (listed in the directory record; not cited for any claim on this page)

More E-commerce connectors

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Shipt to work.

Connect Shipt once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio