Instacart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instacart_statusA | Check Instacart login status and session info. Use this to verify authentication before performing other actions. |
| instacart_loginA | Initiate Instacart login flow. Returns a URL and instructions for the user to complete login manually. After logging in, use instacart_status to verify. |
| instacart_logoutA | Clear saved Instacart session and cookies. Use this to log out or reset authentication state. |
| instacart_searchB | Search for products on Instacart. Returns product names, prices, and availability. |
| instacart_add_to_cartB | Add a product to the Instacart cart. Searches for the product and adds the first matching result. |
| instacart_view_cartA | View current Instacart cart contents, including items, quantities, and totals. |
| instacart_clear_cartA | Remove all items from the Instacart cart. |
| instacart_preview_orderB | Preview order before placing. Shows cart summary, delivery window, and any issues that need to be resolved. |
| instacart_place_orderA | Place the order. IMPORTANT: Set confirm=true only when you have explicit user confirmation. Without confirm=true, this returns a preview instead of placing the order. |
| instacart_set_addressC | Set delivery address or zip code for Instacart orders. |
| instacart_storesB | Get list of available stores for the current delivery location. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, instacart_search finds products, instacart_add_to_cart adds them, and instacart_view_cart shows the cart, making misselection unlikely. The tools cover different aspects like authentication, cart management, ordering, and store selection without overlap.
All tool names follow a consistent 'instacart_verb_noun' pattern, such as instacart_add_to_cart and instacart_set_address. This predictable naming scheme enhances readability and helps agents understand the tool's function at a glance, with no deviations in style.
With 11 tools, the server is well-scoped for an Instacart integration, covering essential workflows like login, search, cart management, and ordering. Each tool serves a specific function, and the count is neither too sparse nor bloated, fitting typical server ranges of 3-15 tools.
The tool surface is nearly complete for the Instacart domain, covering core operations from authentication to order placement. Minor gaps exist, such as the lack of tools for updating cart item quantities or removing specific items, but agents can work around these by using clear_cart and re-adding items.