Kroger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KROGER_CLIENT_ID | Yes | Your Kroger API client ID from the Kroger Developer Portal | |
| KROGER_REDIRECT_URI | No | The redirect URI for OAuth2 authentication | http://localhost:8000/callback |
| KROGER_CLIENT_SECRET | Yes | Your Kroger API client secret from the Kroger Developer Portal | |
| KROGER_USER_ZIP_CODE | No | Optional default zip code for location searches |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_locationsC | Search for Kroger store locations near a zip code. |
| get_user_zip_codeA | Returns user zip code, it is anticipated that by exposing this to the LLM it will choose to use it rather than generating a zip code based on system data. Args: N/A Returns: Dictionary containing user Zip Code |
| get_location_detailsB | Get detailed information about a specific Kroger store location. |
| set_preferred_locationB | Set a preferred store location for future operations. |
| get_preferred_locationA | Get the currently set preferred store location. No preferred location is a normal result (preferred_location_id null), not an error. Returns: Dictionary containing the preferred location information |
| check_location_existsB | Check if a location exists in the Kroger system. |
| get_product_imagesA | Get an image for a specific product from the requested perspective. Use get_product_details first to see what perspectives are available (typically "front", "back", "left", "right"). |
| search_productsC | Search for products at a Kroger store. |
| bulk_search_productsB | Search for multiple products in a single tool call to reduce round-trips. |
| get_product_detailsB | Get detailed information about a specific product. |
| search_products_by_idC | Search for products by their specific product ID. |
| add_items_to_cartA | Add a single item to the user's Kroger cart and track it locally. If the user doesn't specifically indicate a preference for pickup or delivery, you should ask them which modality they prefer before calling this tool. |
| bulk_add_to_cartA | Add multiple items to the user's Kroger cart in a single operation. If the user doesn't specifically indicate a preference for pickup or delivery, you should ask them which modality they prefer before calling this tool. |
| view_current_cartA | View the current cart contents tracked locally. Note: This tool can only see items that were added via this MCP server. The Kroger API does not provide permission to query the actual user cart contents. Returns: Dictionary containing current cart items and summary |
| remove_from_cartA | Remove an item from the local cart tracking only. IMPORTANT: This tool CANNOT remove items from the actual Kroger cart in the app/website. It only updates our local tracking to stay in sync. The user must remove the item from their actual cart through the Kroger app or website themselves. Use this tool only when:
|
| clear_current_cartA | Clear all items from the local cart tracking only. IMPORTANT: This tool CANNOT remove items from the actual Kroger cart in the app/website. It only clears our local tracking. The user must remove items from their actual cart through the Kroger app or website themselves. Use this tool only when:
Returns: Dictionary confirming the local cart tracking was cleared |
| mark_order_placedA | Mark the current cart as an order that has been placed and move it to order history. Use this after you've completed checkout on the Kroger website/app. |
| view_order_historyA | View the history of placed orders. Note: This tool can only see orders that were explicitly marked as placed via this MCP server. The Kroger API does not provide permission to query the actual order history from Kroger's systems. |
| list_chainsA | Get a list of all Kroger-owned chains. Returns: Dictionary containing chain information |
| get_chain_detailsC | Get detailed information about a specific Kroger chain. |
| check_chain_existsB | Check if a chain exists in the Kroger system. |
| list_departmentsB | Get a list of all available departments in Kroger stores. Returns: Dictionary containing department information |
| get_department_detailsC | Get detailed information about a specific department. |
| check_department_existsA | Check if a department exists in the Kroger system. |
| get_user_profileA | Get the authenticated user's Kroger profile information. The Identity API needs a sign-in that grants the profile.compact scope. Returns: Dictionary containing user profile data |
| test_authenticationA | Check whether the user is signed in and the saved token has not expired. An expired token is refreshed if possible. The check compares the token's expiry time with the clock, so a sign-in that Kroger revoked early still reports token_valid true until a cart call fails. A user who is not signed in is a normal result (token_valid false), not an error. Returns: Dictionary indicating authentication status |
| get_authentication_infoA | Get information about the current authentication state and token. A user who is not signed in is a normal result (authenticated false), not an error. Returns: Dictionary containing authentication information |
| force_reauthenticateA | Force re-authentication by clearing the current authentication token. Use this if you're having authentication issues or need to log in as a different user. This deletes the saved user token. The local cart tracking and order history are kept. Returns: Dictionary indicating the re-authentication was initiated |
| get_current_datetimeA | Get the current system date and time. This tool is useful for comparing with cart checkout dates, order history, or any other time-sensitive operations. Returns: Dictionary containing current date and time information |
| start_authenticationA | Start the OAuth authentication flow with Kroger. This tool returns a URL that the user needs to open in their browser to authenticate with Kroger. After authorization, the user will be redirected to a callback URL that they need to copy and paste back. If Kroger shows invalid_scope instead of the sign-in page, the app is not registered for one of the requested scopes (the scope field of the result, set by KROGER_USER_SCOPES in the server's configuration). Returns: Dictionary with authorization URL, the requested scopes, and instructions |
| complete_authenticationA | Complete the OAuth flow using the redirect URL from Kroger. After opening the auth URL in your browser and authorizing the app, you'll be redirected to a callback URL. Copy that entire URL and pass it to this tool to complete the authentication process. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| grocery_list_store_path | Generate a prompt asking for the optimal path through a store based on a grocery list. |
| pharmacy_open_check | Generate a prompt asking whether a pharmacy at the preferred Kroger location is open. Returns: A prompt asking about pharmacy status |
| set_preferred_store | Generate a prompt to help the user set their preferred Kroger store. |
| add_recipe_to_cart | Generate a prompt to find a specific recipe and add ingredients to cart. (default: classic apple pie) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools target distinct resources and actions (locations, products, cart, orders, chains, departments). The main overlap is between authentication/status tools and between paired check_* versus get_* detail tools, but the descriptions make the intended use clear enough to avoid serious misselection.
Almost all tools use a readable snake_case verb_noun pattern such as get_location_details, search_products, and add_items_to_cart. Minor deviations like bulk_search_products, force_reauthenticate, and mark_order_placed slightly break the pattern but remain understandable and consistent in casing.
At 31 tools, the surface is heavy for a shopping assistant MCP, with several check_*/get_* pairs and bulk variants inflating the set. The broad domain explains some of it, but many tools could be consolidated or treated as internal helpers.
Core workflows are covered: authentication, store search, product search/details, cart add/view/remove/clear, local order history, chains, departments, and profile. Gaps include no true checkout or cart-quantity update, and cart/order operations are local-only due to Kroger API limits, but the tool descriptions acknowledge these constraints.