Instacart
Instacart Developer Platform APIs to create shoppable lists/recipes and discover nearby retailers
Verdict
Common use cases
- Turn blog recipes into shoppable Instacart links
- Send clients meal-prep lists they can order
- Check grocery delivery coverage by zip code
- Generate shopping carts for team lunches
- Convert ingredient lists into shareable URLs
Integration
- Vendor
- Instacart
- Category
- other
- Auth
- NONE
- Tools
- 3
- Composio slug
instacart
Tools
- Create Recipe Page
Create a recipe page on instacart + return shareable url. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
- Create Shopping List Page
Create a shopping list page on instacart + return shareable url. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
- Get Nearby Retailers
Get nearby retailers by postal code + country code. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Instacart in the MCP directory and click Connect. 3. No authentication is required — the integration activates immediately since it uses Instacart's public API. 4. Open any Space and type '@Instacart' to confirm the MCP appears in the mention menu. 5. Test the connection by asking '@Instacart create a shopping list for chicken, rice, and broccoli' — you should receive a shareable Instacart URL within seconds. 6. If the response mentions a fallback to dev endpoints, the production API may be temporarily unavailable; the link will still work but might behave differently. 7. To invoke specific tools, address the MCP directly in your prompt and describe the recipe or list you want to generate.
What teammates see: by default, memories from Instacart are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Recipe to Cart
@Instacart create a recipe page for chicken tikka masala with basmati rice, naan, and cucumber raita. Include quantities for four servings.Open in a Space →
Weekly Meal Prep
@Instacart create a shopping list for this week's meal prep: overnight oats, grilled chicken salads, stir-fry vegetables, and quinoa bowls. Assume two people eating lunch and dinner.Open in a Space →
Office Snack Run
@Instacart create a shopping list for office snacks: mixed nuts, granola bars, sparkling water, fresh fruit, and dark chocolate. Then check which retailers deliver to zip code 94103.Open in a Space →
Check Delivery Zones
@Instacart get nearby retailers for postal code 10001 in the US. I need to know which stores deliver before I finalize this grocery order.Open in a Space →
Party Ingredient List
@Instacart create a recipe page for taco night: ground beef, tortillas, shredded cheese, salsa, guacamole, sour cream, and lime. Quantities for twelve people.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Instacart create a recipe page for chicken tikka masala with rice and naan, including all ingredients and cooking instructions
I've created an Instacart recipe page for Chicken Tikka Masala with rice and naan. The page includes a full ingredient list (boneless chicken thighs, yogurt, garam masala, ginger, garlic, tomato sauce, heavy cream, basmati rice, naan bread) and step-by-step cooking instructions. You can view and share the recipe here: https://www.instacart.com/recipe/chicken-tikka-masala-dinner-abc123. Anyone with this link can add all ingredients to their Instacart cart in one click.
This example shows the MCP's recipe-creation capability, which generates a shareable page that bundles ingredients with instructions. The tool attempts production first, then falls back to a dev environment if needed—useful for testing, but means the URL domain may vary. No authentication is required, so any Space member can generate recipe pages.
@Instacart build me a shopping list for a weekend BBQ: burgers, hot dogs, buns, chips, soda, and watermelon
I've created an Instacart shopping list page for your weekend BBQ. The list includes ground beef for burgers, hot dogs, hamburger and hot dog buns, assorted chips, soda variety pack, and a seedless watermelon. Here's your shareable link: https://www.instacart.com/list/weekend-bbq-xyz789. You or anyone you share this with can review the items, adjust quantities, and check out directly through Instacart for same-day delivery.
This demonstrates the shopping-list tool, which converts a casual list into a shareable Instacart page. The MCP doesn't select specific brands or quantities—those are inferred defaults that users refine in the Instacart UI. Like the recipe tool, this falls back to dev if production fails, so confirm the URL environment before sharing widely.
@Instacart what grocery retailers deliver to postal code 94103 in the US? I need same-day options.
For postal code 94103 (San Francisco, CA), Instacart partners with several retailers offering same-day delivery: Safeway (typically 1-2 hour windows), Whole Foods Market (via Amazon partnership, 2-hour delivery), Costco (same-day available for members), CVS Pharmacy (convenience items, 1-hour express option), and Trader Joe's (limited same-day slots). Availability and delivery fees vary by time of day and demand. This is an illustrative summary—actual retailer list and delivery windows depend on real-time Instacart API data for your location.
This example uses the get-nearby-retailers tool to scope delivery options by postal code and country. It's a read-only query with no side effects, useful for location-aware shopping recommendations. The MCP attempts production first, so results reflect live retailer partnerships—but note that delivery availability changes throughout the day based on shopper capacity.
Use-case deep-dives
When Instacart MCP simplifies group grocery coordination
A 6-person remote team planning a quarterly offsite in a rented house hits the grocery coordination problem: who buys what, and how do you avoid duplicate runs? The Instacart MCP solves this by letting the team build a shared shopping list in Switchy during planning, then generating a single shareable Instacart URL that anyone can claim and fulfill. The recipe page tool works if you're meal-planning from scratch, but most teams already have a menu doc and just need the list consolidation. The nearby retailers lookup is useful if you're unsure which stores serve the rental's zip code. This is a low-frequency, high-value scenario—if your team does quarterly or annual offsites and someone always ends up making three grocery trips, this MCP pays for itself in saved time and goodwill.
How food content teams use this for recipe development
A 3-person food blog or YouTube channel team testing recipes needs to move from brainstorm to ingredient procurement fast. The Instacart MCP's recipe page tool lets them draft a recipe in Switchy, generate an Instacart page with one click, and share it with a test cook or sponsor. This works best for teams publishing 2-4 recipes a week where speed matters more than custom formatting—Instacart's recipe page layout is fixed, so if you need brand-specific styling, you'll still export to your CMS. The shopping list tool is less useful here unless you're batching ingredient orders across multiple recipes. If your workflow is already Instacart-native for personal use, this MCP just formalizes it inside your team workspace and cuts the copy-paste step.
When this MCP supports onboarding but not core ops
A meal kit or nutrition coaching startup with 2-3 customer success reps uses the Instacart MCP to generate shopping lists for clients who want to try recipes outside the subscription box. The use case is real but narrow: it's a nice-to-have for onboarding or churn recovery, not a daily driver. The MCP has no read or search capability, so you can't pull existing Instacart data or check client order history—it's purely outbound list creation. If your CS team is already sending clients to Instacart manually, this automates the URL generation and keeps the workflow in Switchy. But if you need two-way sync or order tracking, you'll hit the tool ceiling fast. Best for teams doing fewer than 10 custom lists a week where the manual step is annoying but not blocking.
Frequently asked
What does the Instacart MCP do in Switchy?
It creates shareable Instacart recipe pages and shopping lists directly from your AI conversations, plus looks up nearby grocery retailers by postal code. You can turn a meal plan or ingredient list into a clickable Instacart URL without leaving Switchy. No manual copy-paste into the Instacart app.
Does the Instacart MCP require authentication or API keys?
No. This MCP uses Instacart's public endpoints, so you don't need an Instacart account, API key, or OAuth flow to generate recipe and shopping list pages. Anyone on your team can use it immediately after enabling the integration in Switchy.
Can it place actual Instacart orders or check inventory?
No. The MCP only creates shareable pages — it doesn't place orders, check real-time stock, or access your Instacart cart. Someone still has to click the generated URL, review the items, and check out manually in Instacart. Think of it as a smart link generator, not a checkout bot.
How is this better than just pasting a list into Instacart myself?
Speed and context. If your AI already generated a recipe or meal plan, the MCP turns it into a clickable Instacart page in one step. You skip the manual reformatting and item-by-item search. Useful for teams running meal-prep workflows or client nutrition plans where you share shopping links frequently.
Who on my team should enable the Instacart MCP?
Anyone who generates shopping lists or recipes in Switchy and wants to share them as Instacart links. Common in food-focused teams — nutritionists, meal-kit ops, recipe bloggers. No special permissions needed since there's no auth. It doesn't count against Instacart rate limits because it uses public endpoints.