Instacart MCP server icon

Instacart

by Instacart

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Productivity2 tools

Search grocery products and build an Instacart cart from your AI agent. Anthropic lists 2 tools. The cart syncs to your Instacart account — you check out in Instacart's own app, and no tool spends money.

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.

Connect Instacart via MCP

https://fig-mcp.instacart.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Instacart Tools & Capabilities (2)

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

Limits

  • No checkout, by design. Nothing here submits an order or takes payment. If you want the agent to complete a purchase, this connector cannot, and the last step is always yours in Instacart.
  • Instacart publishes no tool list. The two names come from Anthropic's directory. We could not diff them against a vendor enumeration because none exists, and the OAuth gate meant we could not read the live list either.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here — including the cart tool's operation set, which is the detail a reader most wants.
  • One OAuth scope covers everything. connect:fig_mcp does not separate reading from cart modification, so consent is all-or-nothing across the two tools.
  • Self-service setup is not available. No dynamic client registration, and Instacart's docs route access through a partner representative.
  • United States only. Instacart names the U.S. as the availability region for the Claude integration.
  • Rate limits are unpublished. Instacart's MCP documentation directs partners to their representative for "rate limits, and monitoring" rather than stating any figure.
  • The changelog is nearly empty. Instacart's MCP changelog carries a single entry, dated 2026-03-15, recording that the documentation site was published. There is no public record of tool changes, so a silent rename or addition would not be visible from outside.
  • Substitutions are the agent's blind spot. The documentation describes swapping products, and grocery inventory changes between cart-building and checkout. Review what is actually in the cart rather than trusting the conversation's summary of it.

Frequently asked questions

No. It builds a cart and hands it back to you. Instacart states that any cart you build stays in sync with your account so you can pick up where you left off in the app or on the website whenever you are ready to order. A hands-on test found Claude supplied a link that opened the Instacart cart, where the reviewer completed the purchase.

Anthropic's directory lists two, named cart and search_products. Instacart publishes no tool list of its own anywhere in its MCP documentation, so there is no second enumeration to check the two against. The endpoint requires OAuth, so we could not read the live list either. Treat two as the directory's count rather than a verified total.

One scope, connect:fig_mcp, which the server advertised in its own RFC 9728 descriptor on 2026-08-22. It names the connector rather than any action, so there is no way to grant product search without also granting cart modification. Instacart's directory entry summarises the permission as read and write.

Almost certainly it multiplexes, and the tool name alone cannot tell you which operations. Instacart's documentation says the server can add, swap, or remove products and track the current order state, which is four behaviours behind one noun-shaped name. We could not read the schema because the endpoint is gated, so the enum is unverified.

There are two, and they are unrelated. The connector in Anthropic's directory is fig-mcp.instacart.com, OAuth-gated, for grocery carts. Instacart's Developer Platform runs a separate API-key server at mcp.instacart.com whose tools create recipe and shopping-list pages. Our anonymous handshake on 2026-08-22 identified the latter as InstacartRecipeServer.

Not without Instacart provisioning you. Its documentation says to contact your Instacart representative for onboarding, access provisioning, and your MCP endpoint URL. The authorization server published no registration endpoint on 2026-08-22, so a client cannot register itself. The consumer connector is reached through Claude's directory instead.

The United States only. Instacart states the Claude integration is available on mobile and web for users in the U.S., and the account linking prompt appears when you start a grocery conversation. Instacart's marketplace serves North America, so store availability, inventory and delivery are all tied to a US address.

Your Instacart account's personalised shopping context. Instacart says Claude surfaces personalised results from your account and live inventory from nearby stores, which implies your location and buying history shape what comes back. Anthropic states connector data is not used to train its models and that the app cannot see your other conversations.

Sources

Use in Agentman

Connect 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

Server Info

Category
Productivity
Developer
Instacart
Tools
2
Domain
fig-mcp.instacart.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.